Couchbase Server

[RN 2.0.2] Adding node in the middle of the rebalance should be allowed and should not affect on-going rebalance

Details

  • Flagged:
    Release Note

Description

This bug was found in with http://www.couchbase.com/issues/browse/MB-6007

Logs are attached on there.

Currently we're seeing rebalance to fail due to detected_nodes_change which purpose is to detect crashes of nodes that participate in rebalance.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Aleksey Kondratenko added a comment -
Aliaksey has patch in gerrit
Show
Aleksey Kondratenko added a comment - Aliaksey has patch in gerrit
Hide
Permalink
Aliaksey Artamonau added a comment -
http://review.couchbase.org/23559
Show
Aliaksey Artamonau added a comment - http://review.couchbase.org/23559
Hide
Permalink
Karen Zeller added a comment -
Nominating for RN 2.0.1
Show
Karen Zeller added a comment - Nominating for RN 2.0.1
Hide
Permalink
Karen Zeller added a comment -
From AlkK: known issue in 2.0.1, fixed for 2.0.2
Show
Karen Zeller added a comment - From AlkK: known issue in 2.0.1, fixed for 2.0.2
Hide
Permalink
Aliaksey Artamonau added a comment -
Actually its fixed in 2.0.1
Show
Aliaksey Artamonau added a comment - Actually its fixed in 2.0.1
Hide
Permalink
Aliaksey Artamonau added a comment -
Sorry, ignore my comment. It's not merged to 2.0.1 branch indeed.
Show
Aliaksey Artamonau added a comment - Sorry, ignore my comment. It's not merged to 2.0.1 branch indeed.
Hide
Permalink
Karen Zeller added a comment -
Added as RN 2.0.1:

If you try to add a node during cluster rebalance, the
rebalance may fail and return the messages <literal>{detected_nodes_change</literal>
or <literal>{ns_node_disco_events</literal>. To avoid this error complete your
cluster rebalance, add the new node and then rebalance once again. This issue will
be fixed in future releases.
Show
Karen Zeller added a comment - Added as RN 2.0.1: If you try to add a node during cluster rebalance, the rebalance may fail and return the messages <literal>{detected_nodes_change</literal> or <literal>{ns_node_disco_events</literal>. To avoid this error complete your cluster rebalance, add the new node and then rebalance once again. This issue will be fixed in future releases.
Hide
Permalink
Karen Zeller added a comment -
See previous RN 2.0.1 entry in comment.
Show
Karen Zeller added a comment - See previous RN 2.0.1 entry in comment.
Hide
Permalink
Karen Zeller added a comment -
See previous RN 2.0.1 entry in comment.
Show
Karen Zeller added a comment - See previous RN 2.0.1 entry in comment.

People

  • Assignee:
    Karen Zeller
    Reporter:
    Karan Kumar
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: