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

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • None
    • 4.7.0
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2020-04-20, Repl 2020-05-04, Repl 2020-05-18, Repl 2020-06-01
    • 0

    Description

      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.

      Attachments

        Issue Links

          is duplicated by

          Task - A task that needs to be done. SERVER-33878 Update OplogFetcher to go into SyncSource selection on CappedPositionLost error

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-47271 Update oplog fetcher to return an InvalidSyncSource error only when the former sync source should be blacklisted

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-47272 Update bgsync to blacklist invalid sync sources

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-71156 Fatal Assertion 40507 UnrecoverableRollbackError and Mongo Crash with 4.0.27 WT

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-33878 Update OplogFetcher to go into SyncSource selection on CappedPositionLost error

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-27403 Consider term and rbid when validating the proposed sync source

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-27980 Secondary tries to rollback when it lagged to much behind primary

          • Major - P3 - Major loss of function.
          • Closed
          mentioned in

          Page Loading...

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: