[MB-6751] Incorrect error message from 'vkey' when key does not exist Created: 26/Sep/12  Updated: 26/Oct/12  Resolved: 26/Sep/12

Status: Resolved
Project: Couchbase Server
Component/s: couchbase-bucket
Affects Version/s: 2.0
Fix Version/s: 2.0-beta-2
Security Level: Public

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: Mike Wiederhold
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Not sure if this is the server sending back the wrong message, or the stats script malforming the commend.

Running this command:
/opt/couchbase/bin/cbstats localhost:11210 vkey pkrug 316
Stats 'vkey pkrug 316' are not available from the requested engine.

In 1.8, it would return "not found" because the request is valid, but the key is not there. In 2.0, something changed and now it doesn't actually recognize the command which leads to confusion with the error response.

Comment by Chiyoung Seo [ 26/Sep/12 ]

Please take a look at this issue when you have time. It seems to me that this is the regression from our recent changes in stats key to support the OBSERVE command.
Comment by Mike Wiederhold [ 26/Sep/12 ]
Comment by Thuan Nguyen [ 27/Sep/12 ]
Integrated in github-ep-engine-2-0 #435 (See [http://qa.hq.northscale.net/job/github-ep-engine-2-0/435/])
    MB-6751: Fix vkey not found in cbstats script (Revision fdecb33cb44a99f3c2b62c324042ca569cd5591d)

     Result = SUCCESS
Mike Wiederhold :
Files :
* management/cbstats
Comment by kzeller [ 26/Oct/12 ]
RN: Incorrect message had been sent in response to
a cbstats vkey command. Server had returned the string 'not found'
for valid request. Now correct the memcached protocol
error is returned.
Generated at Wed Sep 17 13:46:51 CDT 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.