Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-69158

Donor waits for majority committed no-op write on recipient primary

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Server Serverless 2022-09-05

    Description

      The final step of the shard split critical section must wait for a no-op write to majority commit on the recipient primary to prevent invariant rollback of the stable_timestamp on the recipient. If the node selected to be recipient primary goes down after winning an election, another node with a lower lastApplied may win a subsequent election and force the original primary to rollback when it comes back online. Waiting for the selected recipient primary to majority commit a no-op entry while its primary ensures future elections will not cause this rollback.

      Attachments

        Activity

          People

            matt.broadstone@mongodb.com Matt Broadstone
            matt.broadstone@mongodb.com Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: