Details
-
Improvement
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
4
-
true
Description
There are multiple changes to replication behavior on stepdown/shutdown. Some are in for RC0, others for RC1+; ticket scope is likely to expand.
See linked; at minimum the primary blocks immediately and then waits a configurable number of seconds for a secondary to be fully caught up. If this catch-up doesn't occur in the specified number of seconds and the ``force`` flag is ``false``, the stepdown/shutdown fails.
Attachments
Issue Links
- documents
-
SERVER-16377 Require 'force' argument to stepdown or shutdown a node in a single-node replica set
-
- Closed
-
-
SERVER-14251 Change shutdown/stepdown to block writes and wait until at least 1 electable secondary is fully caught up
-
- Closed
-
-
SERVER-14444 Implement stepdown functionality in the new ReplicationCoordinator
-
- Closed
-
-
SERVER-15310 kill all operations before attempting stepdown
-
- Closed
-
-
SERVER-15861 Add argument to replSetStepDown to allow users to specify how long to wait for secondaries to catch up
-
- Closed
-
- is duplicated by
-
DOCS-4328 Document revised stepdown behavior in new replication coordinator
-
- Closed
-