[SERVER-616] Extend stepdown/shutdown command to optionally wait for replica to catch up (hinted handoff) Created: 09/Feb/10  Updated: 12/Jul/16  Resolved: 10/Jun/11

Status: Closed
Project: Core Server
Component/s: Replication, Usability
Affects Version/s: None
Fix Version/s: 1.9.1

Type: Improvement Priority: Minor - P4
Reporter: Mathias Stearn Assignee: Kristina Chodorow (Inactive)
Resolution: Done Votes: 5
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

should lock master for writes immediately then wait for slave to catch up before shutting down. Ideally could notify slave that it is now master.



 Comments   
Comment by auto [ 10/Jun/11 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: step down before shutting down SERVER-616
Branch: master
https://github.com/mongodb/mongo/commit/30679312d1b11e6ed3c2fece3fcc0b4819142ce6

Comment by Kristina Chodorow (Inactive) [ 10/Jun/11 ]

http://www.mongodb.org/display/DOCS/Starting+and+Stopping+Mongo#StartingandStoppingMongo-SendingshutdownServer%28%29messagefromthemongoshell

Comment by auto [ 10/Jun/11 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: added shutdownServer options SERVER-616
Branch: master
https://github.com/mongodb/mongo/commit/5a450f3c4cf4132ed9e82a66f8614064448c3231

Comment by auto [ 10/Jun/11 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: don't shut down if slaves aren't up-to-date SERVER-616
Branch: master
https://github.com/mongodb/mongo/commit/0180e84034448d695ca9b442faf580723aba3435

Comment by Eliot Horowitz (Inactive) [ 13/Aug/10 ]

Its less relevant, as there are other ways to change where the master is.
Still would be nice to just be able to shutdown a master and have it be smart.
Right now with sets, you would just first change the master, then bring down the old one

Comment by AndrewK [ 13/Aug/10 ]

Is this still a relevant issue with regards to replica-sets, or was it only really a problem with replica-pairs?

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