Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Replication
-
Labels:None
-
Backwards Compatibility:Fully Compatible
-
Backport Requested:v4.4, v4.2, v4.0
-
Sprint:Repl 2020-04-20, Repl 2020-05-04
Description
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.
Attachments
Issue Links
- is documented by
-
DOCS-13609 Investigate changes in SERVER-47190: Shutdown command with force:true should ignore all stepdown errors
-
- Resolved
-
- is related to
-
SERVER-32679 shutdown command fails on single node replica set for timeoutSecs >= 120
-
- Open
-