Description
Problem
The fix for MB-45110 in ns_server allows nodes that already regularly failed over to be subsequently unsafely failed over. We should permit this also in the CLI. Essentially if the --force option is passed to the CLI when failover is invoked, we should permit it to be applied to nodes that are in the inactiveFailed state. This is needed so clusters don't get stuck as they can do as described in MB-45110.
Steps to reproduce
1. Create a 5 node cluster: .137, .138, .139, .140, .142
2. Stop-server on .140 and when the node becomes unresponsive, fail it over, but don't rebalance it out yet.
3. Now stop server on .138, .139 nodes.
4. --force failover of node .138, .139 and .140
Attachments
Issue Links
- relates to
-
MB-45110 [Chronicle] Cluster can get potentially stuck such that we may not be able to remove failed nodes out of the cluster
-
- Closed
-
| For Gerrit Dashboard: MB-45462 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 150583,3 | MB-45462 Allow failover of inactiveNodes | master | couchbase-cli | Status: MERGED | +2 | +1 |
| 150651,3 | MB-45462 Allow failover of inactiveAdded nodes | master | couchbase-cli | Status: MERGED | +2 | +1 |