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

do a second majority write on oldPrimary before committed read in read_committed_after_rollback.js

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.1, 3.7.1
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v3.6
    • 0

      The secondary can lose it's sync source after it replicates the new write, but before it gets the new committed optime here. Doing a second write should ensure that the new committed optime gets propagated.

            Assignee:
            judah.schvimer@mongodb.com Judah Schvimer
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: