Uploaded image for project: 'Java Couchbase JVM Core'
  1. Java Couchbase JVM Core
  2. JVMCBC-564

In bucket config payload, Java client uses nodesExt node list as servers for bucket



    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • None
    • .backlog, 1.6.2
    • Config Management, Core
    • None
    • 1


      The bucket payload contains 2 lists of nodes:

      1. the nodes list
      2. the nodesExt list

      The nodes contains the nodes on which this bucket is deployed. It is the case that there will be a time lag between when the node shows up in the nodes list and when the bucket is created on the node in question, but it eventually will be there. For couchbase buckets, it will be some further time before a vbucket is created on this node - and obviously for this refer to the vbucket map.

      The nodesExt is a global list (i.e. not specific to the bucket) of all active nodes in the cluster. This list contains information about the node such as hostname and the services that are running on this node along with the associated ports. There may be more nodes in the nodesExt list than are in the nodes list (e.g. N1QL or 2i only nodes will show in the nodesExt list but not in the nodes list.)

      In the case of memcached buckets assuming that the bucket is present on all nodes can lead to problems during transitions such as delta node recovery situations where the bucket is not yet on the node.


        Issue Links

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


            There are no comments yet on this issue.


              daschl Michael Nitschinger
              dfinlay Dave Finlay
              0 Vote for this issue
              1 Start watching this issue