-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
v4.4, v4.2, v4.0
-
Repl 2020-04-20, Repl 2020-05-04
The shutdown command returns an error if stepdown fails with any error code other than NotMaster, even if force:true is specified. This can fail with InterruptedDueToReplStateChange if there is a concurrent stepdown in progress, since it kills user operations that take certain locks. In contrast, signal-based shutdown ignores all stepdown errors and proceeds with the shutdown. It is expected that shutdown with force:true would always shut down the server, so we should make it behave like signal-based shutdown.
- is related to
-
SERVER-32679 shutdown command fails on single node replica set for timeoutSecs >= 120
- Backlog
-
SERVER-81115 ReplicaSetAwareService Can Be Shutdown While Node is Still Primary
- Open