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

Do not go into rollback due to falling off the back of your sync source's oplog

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2020-04-20, Repl 2020-05-04, Repl 2020-05-18, Repl 2020-06-01
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently we treat falling off the back of the oplog the same as being on a divergent branch of history here. Before deciding to go into rollback, we should check if we've fallen off the back of our sync source's oplog and if so switch sync sources (with an InvalidSyncSource error) instead of rolling back (OplogStartMissing error). We can do this exactly the same as how it's done in the SyncSourceResolver by comparing our last fetched optime to the sync source's oldest optime.

            Assignee:
            xuerui.fa@mongodb.com Xuerui Fa
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            1 Vote for this issue
            Watchers:
            24 Start watching this issue

              Created:
              Updated:
              Resolved: