-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Repl 2021-10-18
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Calling shutdown on a primary can fail with PrimarySteppedDown error if the primary has either:
- already stepped down
- is currently going through an unconditional stepdown
- a new term has been detected
Instead of having users retry the shutdown command on this error, we should consider having shutdown succeed if 1) has happened, or wait for the concurrent stepdown to complete for 2), 3).
- related to
-
SERVER-60699 Investigate more frequent occurences of PrimarySteppedDown errors during replica set shutdown in 5.1
-
- Closed
-
- mentioned in
-
Page Loading...