Description
We currently allow new nodes to be added while rebalance is ongoing. This used to be ok previously but in 6.5 we try to synchronize the config after updating the vbucket map at the end of vbucket move. This synchronization step can fail if a new node is added to the cluster and the config sync request is sent to the new node while it's getting initialized.
Attachments
Issue Links
- relates to
-
MB-34846 rebalance failure in centos longevity with failed_to_update_vbucket_map error
- Closed