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

    XMLWordPrintable

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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: