Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.1.0
    • Component/s: Documentation
    • 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.

      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        ingenthr Matt Ingenthron created issue -
        Hide
        SteveC 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
        SteveC 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
        ingenthr Matt Ingenthron added a comment -

        Yes, should be INFO log level. I think this is fixed, but we'll check.

        Show
        ingenthr Matt Ingenthron added a comment - Yes, should be INFO log level. I think this is fixed, but we'll check.
        rags Raghavan Srinivas (Inactive) made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 1.1beta [ 10370 ]
        Resolution Incomplete [ 4 ]
        rags Raghavan Srinivas (Inactive) made changes -
        Resolution Incomplete [ 4 ]
        Status Resolved [ 5 ] Reopened [ 4 ]
        ingenthr Matt Ingenthron made changes -
        Assignee Raghavan Srinivas [ rags ] Michael Nitschinger [ daschl ]
        Hide
        daschl 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
        daschl 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
        daschl Michael Nitschinger made changes -
        Assignee Michael Nitschinger [ daschl ] Matt Ingenthron [ ingenthr ]
        ingenthr Matt Ingenthron made changes -
        Fix Version/s 1.1.0 [ 10274 ]
        Fix Version/s 1.1-beta [ 10370 ]
        daschl Michael Nitschinger made changes -
        Fix Version/s 1.1.1 [ 10430 ]
        Fix Version/s 1.1.0 [ 10274 ]
        daschl Michael Nitschinger made changes -
        Fix Version/s 1.1.2 [ 10480 ]
        Fix Version/s 1.1.1 [ 10430 ]
        daschl Michael Nitschinger made changes -
        Fix Version/s 1.1.3 [ 10496 ]
        Fix Version/s 1.1.2 [ 10480 ]
        Hide
        ingenthr 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
        ingenthr 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.
        ingenthr Matt Ingenthron made changes -
        Status Reopened [ 4 ] Resolved [ 5 ]
        Fix Version/s 1.1.0 [ 10274 ]
        Fix Version/s 1.1.3 [ 10496 ]
        Resolution Fixed [ 1 ]
        ingenthr Matt Ingenthron made changes -
        Planned Start (set to new fixed version's start date)
        Planned End (set to new fixed version's start date)
        ingenthr Matt Ingenthron made changes -
        Workflow jira [ 16479 ] Couchbase SDK Workflow [ 38315 ]

          People

          • Assignee:
            ingenthr Matt Ingenthron
            Reporter:
            ingenthr Matt Ingenthron
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes