-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
ALL
If the user performs a stepDown on an otherwise healthy PRIMARY and the SECONDARY has N seconds of lag, then that N seconds of activity is lost. If the PRIMARY is otherwise OK, then the SECONDARY should try to consume all possible oplog while the election takes place (no activity to cluster during this time).
This allows users to call stepDown on busy sets that may always have lag and ensure they aren't dropping data on the floor when they don't need to.
- duplicates
-
SERVER-15861 Add argument to replSetStepDown to allow users to specify how long to wait for secondaries to catch up
- Closed