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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.1, 3.7.1
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.6
    • Linked BF Score:
      0

      Description

      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.

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved: