[JCBC-30] document warning on not-my-vbucket errors Created: 05/Apr/12 Updated: 27/Feb/13 Resolved: 27/Feb/13
|Project:||Couchbase Java Client|
|Reporter:||Matt Ingenthron||Assignee:||Matt Ingenthron|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
During rebalance, WARNING level errors such as
WARN com.couchbase.client.CouchbaseConnection: Reschedule read op due to NOT_MY_VBUCKET error: Cmd: 0 Opaque: 460 Key: membase-test-key-24
can come up. These are safe to ignore, as long as they're small in number and do not persist for a long period of time.
This needs to be documented somewhere in the manuals.
|Comment by Steven Cooke [ 16/May/12 ]|
If safe to ignore, should the log level be INFO?
When I see this error, couchbase reads fail with and the bucket being queried reindexes itself. The bucket is not readable during this period. Writes, however, seem ok
Not sure if it is related or just a UI error, but the Admin console reports "-2929743.01979 resident %" under vbucket resources
|Comment by Matt Ingenthron [ 29/Aug/12 ]|
|Yes, should be INFO log level. I think this is fixed, but we'll check.|
|Comment by Michael Nitschinger [ 13/Nov/12 ]|
In spy the mentioned log message is now a DEBUG. does this resolve the issue or is there something more to it?|
I wonder because its a "docs" issue and I don't see specific info on what to document here.
If not, we can safely close this one I think.
|Comment by Matt Ingenthron [ 27/Feb/13 ]|
This was fixed back in May of 2011. There is no longer a warning.
Note that there have been a couple of reported circumstances where users had an old spymemcached (which we do not prevent or warn against), and they'd still see these warnings.