[DOCS-13609] Investigate changes in SERVER-47190: Shutdown command with force:true should ignore all stepdown errors Created: 22/Apr/20  Updated: 13/Nov/23  Due: 01/May/20  Resolved: 16/Jun/20

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.2.7, 4.4.0-rc4, 4.7.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Ravind Kumar (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-47190 Shutdown command with force:true shou... Closed
Participants:
Days since reply: 3 years, 34 weeks, 1 day ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

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.)



 Comments   
Comment by Ravind Kumar (Inactive) [ 16/Jun/20 ]

Backport to 4.0 was declined. We're done here folks

Comment by Githook User [ 26/May/20 ]

Author:

{'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com', 'username': 'rkumar-mongo'}

Message: DOCS-13609: shutdown: force on primaries ignores stepdown failure
Branch: v4.2
https://github.com/mongodb/docs/commit/cc64eba930c1ace86365a93d0d5fa6e905bd5152

Comment by Githook User [ 13/May/20 ]

Author:

{'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com', 'username': 'rkumar-mongo'}

Message: DOCS-13609: shutdown: force on primaries ignores stepdown failure
Branch: v4.2
https://github.com/mongodb/docs/commit/eaa0b38589b42fba5de01a82ffde7c4c3e71bc60

Comment by Ravind Kumar (Inactive) [ 08/May/20 ]

Blocked waiting for backport to 4.0

Comment by Githook User [ 06/May/20 ]

Author:

{'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com', 'username': 'rkumar-mongo'}

Message: DOCS-13609: shutdown: force on primaries ignores stepdown failure
Branch: v4.2.7
https://github.com/mongodb/docs/commit/36e4ddae5487e84bcf6adbaaf157291afeeeef47

Comment by Githook User [ 06/May/20 ]

Author:

{'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com', 'username': 'rkumar-mongo'}

Message: DOCS-13609: shutdown: force on primaries ignores stepdown failure

Extra fixes
Branch: master
https://github.com/mongodb/docs/commit/031fa80a6d0a9cbba05871ab2487315188a5c2ee

Comment by Ravind Kumar (Inactive) [ 01/May/20 ]

code review

Generated at Thu Feb 08 08:08:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.