-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
RPL A (10/09/15)
-
0
When a primary is requested to step down without
{force: true}and secondaries are not caught up, it has to wait until the previously scheduled heartbeats are run to obtain updated liveness information on the secondaries before completing the step down process. This may take a while with a long heartbeat interval. Restarting the heartbeats if the primary cannot step down immediately will ensure that we get the most update information on the secondaries in the cluster.
- depends on
-
SERVER-20673 support enqueue-only operation for GlobalLock
-
- Closed
-
- related to
-
SERVER-20832 step down command should restart heartbeats at most once
-
- Closed
-