[SERVER-15861] Add argument to replSetStepDown to allow users to specify how long to wait for secondaries to catch up Created: 29/Oct/14  Updated: 11/Jul/16  Resolved: 20/Nov/14

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

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

Issue Links:
Depends
depends on SERVER-15997 Make sure stepDown command can be int... Closed
depends on SERVER-1423 reads often aren't possible while in ... Closed
Documented
is documented by DOCS-4349 Document changes to shutdown/stepdown... Closed
Duplicate
is duplicated by SERVER-13995 on stepdown/election, SECONDARY shoul... Closed
Related
is related to SERVER-15877 Give stepdown command some time to le... Closed
is related to SERVER-15946 replSetStepDown without force argumen... Closed
is related to SERVER-14251 Change shutdown/stepdown to block wri... Closed
Tested
Participants:

 Comments   
Comment by Githook User [ 20/Nov/14 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-15861 add secondaryCatchUpPeriodSecs argument to replSetStepDown
Branch: master
https://github.com/mongodb/mongo/commit/9ae1dd37b3fa0a0325d65dc1b6c8101902c1c2a3

Comment by Andy Schwerin [ 05/Nov/14 ]

Before we wrap this issue, we should also make sure that the command is interruptible during the "wait" period, given that it holds a global lock that prevents writes from making progress.

Comment by Spencer Brody (Inactive) [ 29/Oct/14 ]

This depends on SERVER-1423 because the same locking functionality that will support fsync+lock not blocking readers would allow stepDown to block writes without blocking reads on the oplog. We need that functionality or we can't allow users to specify arbitrarily long wait times as that would block all writes to the system while waiting for secondaries to catch up, which may never happen if a write comes in and that blocks secondaries from reading the oplog.

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