Affects Version/s: 7.0
Fix Version/s: None
Background failover thread checks for bad replicas. In case one is found it tries to create it on another node. Then it waits for the new replica to show up in the cluster state. It waits even if the core creation (initiated by itself) fails.
This situation does not occur on the happy path of the failover cases because the new node was marked as alive. But in case the cluster is in an instable state, or user is restarting the new node, or overseer is overloaded this extra wait will result in holding up this failover thread.
Proposed solution may be
- wait for the result of the core creation
- only if previous step is successful proceed to wait for cluster state change
In such case we could consider moving core creation into the failover thread from the updateExecutor.
I can post a patch with these changes if the solution seems appropriate.