[SERVER-16389] Try to stepdown before shutting down, even when using 'force' Created: 02/Dec/14  Updated: 04/Dec/14  Resolved: 03/Dec/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 2.8.0-rc2

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Currently if you specify

{force:true}

to the shutdown command, we completely skip the step of trying to wait for a secondary to catch up and step down before shutting down the primary. Instead we should block writes and try to wait for a secondary to catch up, but then proceed anyway even if no secondary does actually catch up in time. This will match the behavior of stepdown which was changed in 2.8 to behave like this already.



 Comments   
Comment by Githook User [ 03/Dec/14 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-16389 Clean up behavior of shutdown command waiting for replication
Branch: master
https://github.com/mongodb/mongo/commit/6c93bae163d0cbd4acf8e127c902844353b72c6b

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