Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-551

resync secondaries from scratch after forcing a node to become primary when a majority of nodes is down

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • Server_Docs_20231030
    • Affects Version/s: None
    • Component/s: manual
    • Labels:
      None

      "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

            Assignee:
            Unassigned Unassigned
            Reporter:
            jenna Jenna deBoisblanc
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:
              11 years, 33 weeks, 4 days ago