[DOCS-4349] Document changes to shutdown/stepdown in replication Created: 11/Nov/14  Updated: 16/Mar/15  Resolved: 11/Dec/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v1.3.15, mongodb-3.0

Type: Improvement Priority: Major - P3
Reporter: Michael Paik Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-16377 Require 'force' argument to stepdown ... Closed
documents SERVER-14251 Change shutdown/stepdown to block wri... Closed
documents SERVER-14444 Implement stepdown functionality in t... Closed
documents SERVER-15310 kill all operations before attempting... Closed
documents SERVER-15861 Add argument to replSetStepDown to al... Closed
Duplicate
is duplicated by DOCS-4328 Document revised stepdown behavior in... Closed
Participants:
Days since reply: 9 years, 9 weeks ago

 Description   

There are multiple changes to replication behavior on stepdown/shutdown. Some are in for RC0, others for RC1+; ticket scope is likely to expand.

See linked; at minimum the primary blocks immediately and then waits a configurable number of seconds for a secondary to be fully caught up. If this catch-up doesn't occur in the specified number of seconds and the ``force`` flag is ``false``, the stepdown/shutdown fails.



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

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-4349: release notes/compatibility note for rs stepdown
Branch: master
https://github.com/mongodb/docs/commit/01ca0cbc326e2289af614d2ca24d78df592de582

Comment by Githook User [ 17/Dec/14 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-4349: additional options for replSetStepDown
Branch: master
https://github.com/mongodb/docs/commit/dcd4eeff074779c548bb184113cd2557a6ef0300

Comment by Githook User [ 17/Dec/14 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-4349: step down kills long runing user operations
Branch: master
https://github.com/mongodb/docs/commit/3f907e6a8ac09f7494bdad1f2501208640841017

Comment by Githook User [ 17/Dec/14 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-4349: clarify stepDown force
Branch: master
https://github.com/mongodb/docs/commit/f413a6ac228851cd3b7e591af546ac18bd82a8b5

Comment by Githook User [ 17/Dec/14 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-4349: changed replSetStepDown behavior
Branch: master
https://github.com/mongodb/docs/commit/33b4fe8348dde3903da5680362ee8e934b00f31c

Comment by Spencer Brody (Inactive) [ 24/Nov/14 ]

One interesting piece of behavior that surprised me for a second and may be worth noting is that now you cannot stepDown() a primary in the first 30 seconds after it is elected (unless you use "force"). This is because we don't allow you to stepdown unless there is at least one electable secondary caught up, and secondaries won't vote for anyone, including themselves, if they've voted for someone else in the last 30 seconds.

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