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

During rollback (or w/minvalid invalid) select sync source based on end OpTime

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • ALL
    • Repl 2016-11-21
    • 0

    Description

      If we use the lastFetchedOptime, which is also the common point found during rollback, it is possible that a sync source is selected which will cause the rollback to be attempted again (after the first says it succeeds), but while in an inconsistent state (with minvalid showing an invalid state, needing to apply before being consistent).

      By using the end of minvalid bounds as a criteria for sync source selection it will not be possible to do another rollback until the first has completed and apply all necessary options to get into a consistent state.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-27277 [rsBackgroundSync] Fatal assertion 18750 UnrecoverableRollbackError on numerous 3.2.10 replica sets

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-28056 rollback fail

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-25026 Secondary abort immediately following losing Primary election, will not restart

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-27547 Adjust the system time . then MongoDB status maintian RECOVERING

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-27676 Mongod is not able to restart after OOM kill

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

          Task - A task that needs to be done. SERVER-25861 Adjust minValid logic

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-21537 chainingAllowed = false not being enforced after rs.stepDown()

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-21988 Rollback does not wait for applier to finish before starting

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-23070 rewrite SyncSourceResolver to select sync source asynchronously

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-27050 Ensure upstream node doesn't roll back after checking minvald

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-25848 Enforce single sync source during rollback

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-26415 Make sure to catch up to minValid before exiting rollback

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-26922 minvalid2 should wait for arbiter to be up before shutting secondary down.

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-26972 BackgroundSync should compare minValidSaved to _lastOpTimeFetched

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

          Activity

            People

              spencer@mongodb.com Spencer Brody (Inactive)
              scotthernandez Scott Hernandez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              19 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: