Couchbase Java Client

document warning on not-my-vbucket errors

Details

  • Type: New Feature New Feature
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.1.0
  • Component/s: docs
  • Security Level: Public
  • Labels:
    None

Description

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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Steven Cooke added a comment -
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
Show
Steven Cooke added a comment - 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
Hide
Permalink
Matt Ingenthron added a comment -
Yes, should be INFO log level. I think this is fixed, but we'll check.
Show
Matt Ingenthron added a comment - Yes, should be INFO log level. I think this is fixed, but we'll check.
Hide
Permalink
Michael Nitschinger added a comment -
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.

Thanks,
Michael
Show
Michael Nitschinger added a comment - 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. Thanks, Michael
Hide
Permalink
Matt Ingenthron added a comment -
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.
Show
Matt Ingenthron added a comment - 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.

People

  • Assignee:
    Matt Ingenthron
    Reporter:
    Matt Ingenthron
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: