-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
None
Description
It is a bit ambitious in the current documentation what the force option in the shutdown command means. https://docs.mongodb.com/manual/reference/command/shutdown/
But in implementation prior to this ticket, force means "force to stepDown" the primary. And if force stepDown fails, the shutdown will also fail. But this is no longer true after SERVER-47190.
This ticket slightly changed the semantics of the force option. Now specifying force in shutdown command would ignore all errors during the shutdown process and will shut down the mongod process regardless. Therefore, we should make it clear to users the shutdown command with {force: true} will shut down the server no matter what.
Description of Linked Ticket
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.
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
- documents
-
SERVER-47190 Shutdown command with force:true should ignore all stepdown errors
-
- Closed
-