Uploaded image for project: 'Couchbase .NET client library'
  1. Couchbase .NET client library
  2. NCBC-507

View {0} was mapped to a dead node, failing

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • 1.3.6
    • backlog-1.0
    • process
    • Couchbase 2.2 server on unbuntu, dot net website running in ISS.

    Description

      View

      {0}

      was mapped to a dead node, failing .

      Known issue with previous versions of the couchbase client, see http://www.couchbase.com/issues/browse/NCBC-337 for instance but there are more,
      has some how returned.
      I reverted back to the 1.3.5 client and the error magically disappeared.

      Attachments

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

        Activity

          jmorris Jeff Morris added a comment -

          douwequerty -

          Be aware that we have added additional logging and retry logging in the 1.3.X versions of the client. The retry logic is for handling scenarios when the cluster is transitioning between states, for instance during a rebalance or when a node is added or removed. It's a Warn, because in subsequent retries it's likely that an active node will be selected and the operation will succeed.

          Is this the error that your getting from your OperationResult.Message property or what you are seeing in your logs? The most important result is the final outcome of the operation and what you would see at your at application level and not in your logs.

          That being said, how often is this happening? What is the state of the cluster when this is happening? What about at the app server level - is IIS doing an app-pool refresh at this time?

          If you can supply answers to those questions and logs, it would be helpful in diagnosing what is going on here.

          -Jeff

          jmorris Jeff Morris added a comment - douwequerty - Be aware that we have added additional logging and retry logging in the 1.3.X versions of the client. The retry logic is for handling scenarios when the cluster is transitioning between states, for instance during a rebalance or when a node is added or removed. It's a Warn, because in subsequent retries it's likely that an active node will be selected and the operation will succeed. Is this the error that your getting from your OperationResult.Message property or what you are seeing in your logs? The most important result is the final outcome of the operation and what you would see at your at application level and not in your logs. That being said, how often is this happening? What is the state of the cluster when this is happening? What about at the app server level - is IIS doing an app-pool refresh at this time? If you can supply answers to those questions and logs, it would be helpful in diagnosing what is going on here. -Jeff

          People

            jmorris Jeff Morris
            douwequerty douwequerty
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty