[DOCS-551] resync secondaries from scratch after forcing a node to become primary when a majority of nodes is down Created: 25/Sep/12  Updated: 30/Oct/23  Resolved: 27/Sep/12

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Jenna deBoisblanc Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 11 years, 20 weeks, 2 days ago

 Description   

"Once you add the removed hosts back into the set, they will will detect that they have been added and synchronize to the current state of the set. Be aware that if the original master was one of the removed nodes, these members may need to rollback."

I was informed that a full resync from the new primary is necessary to prevent data corruption. The secondaries may not correctly enter into a rollback state.

I think that the "break the mirror" technique (described for versions < 2.0) still applies in V2.0 and beyond.

http://www.mongodb.org/display/DOCS/Reconfiguring+a+replica+set+when+members+are+down



 Comments   
Comment by auto [ 01/Oct/12 ]

Author:

{u'date': u'2012-10-01T14:32:13-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: edits: DOCS-561 and DOCS-551 reconfig when members are down
Branch: master
https://github.com/mongodb/docs/commit/5fceaf5946060b31cbab92d88650dffa487ae18d

Comment by auto [ 01/Oct/12 ]

Author:

{u'date': u'2012-09-28T16:02:48-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: merge: DOCS-561 and DOCS-551
Branch: master
https://github.com/mongodb/docs/commit/814530f8937cc2d4bb0c45d10ab3f10aa4cc5a29

Comment by auto [ 01/Oct/12 ]

Author:

{u'date': u'2012-09-27T14:59:48-07:00', u'email': u'bob.grabar@10gen.com', u'name': u'Bob Grabar'}

Message: DOCS-561 & DOCS-551 reconfig repl set when members down: final
Branch: master
https://github.com/mongodb/docs/commit/27a7b3c3ef774a364bd7c2728eea841955b82fe8

Comment by auto [ 01/Oct/12 ]

Author:

{u'date': u'2012-09-27T14:42:20-07:00', u'email': u'bob.grabar@10gen.com', u'name': u'Bob Grabar'}

Message: DOCS-561 & DOCS-551 reconfig repl set when members down: draft 4
Branch: master
https://github.com/mongodb/docs/commit/31c76346910ba5f657f7c5a09225e68094464dab

Comment by auto [ 01/Oct/12 ]

Author:

{u'date': u'2012-09-27T14:15:45-07:00', u'email': u'bob.grabar@10gen.com', u'name': u'Bob Grabar'}

Message: DOCS-561 & DOCS-551 reconfig repl set when members down: draft 3
Branch: master
https://github.com/mongodb/docs/commit/ec6b2d35b985b1e0c664605d9a63b28e51a29d7a

Comment by auto [ 01/Oct/12 ]

Author:

{u'date': u'2012-09-27T12:53:19-07:00', u'email': u'bob.grabar@10gen.com', u'name': u'Bob Grabar'}

Message: DOCS-561 & DOCS-551 reconfig repl set when members down: draft 2
Branch: master
https://github.com/mongodb/docs/commit/bd42f6aa1715d9594230006a556166cc6291b182

Comment by auto [ 01/Oct/12 ]

Author:

{u'date': u'2012-09-27T11:24:18-07:00', u'email': u'bob.grabar@10gen.com', u'name': u'Bob Grabar'}

Message: DOCS-561 & DOCS-551 reconfig repl set when members down: draft 1
Branch: master
https://github.com/mongodb/docs/commit/f6519844ce7efcb56f8e72e56818ef4bd4aa48e0

Comment by Bob Grabar [ 27/Sep/12 ]

Related ticket: https://jira.mongodb.org/browse/DOCS-561

Comment by Bob Grabar [ 27/Sep/12 ]

I'm checking on whether the "break the mirror" technique still applies.

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