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

InitialSyncer::_setup_inlock() should reset last applied and durable optimes.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • 3.4.4, 3.5.6
    • 3.4.7, 3.5.9
    • Replication
    • Fully Compatible
    • ALL
    • Repl 2017-05-08, Repl 2017-05-29, Repl 2017-06-19
    • 0

    Description

      When restarting an initial sync attempt, InitialSync clears user data but does not reset the last applied optime.

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-29436 InitialSyncer doesn't need to update optimes of ReplicationCoordinator until it completes successfully

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Backlog

          Activity

            People

              william.schultz@mongodb.com William Schultz (Inactive)
              benety.goh@mongodb.com Benety Goh
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: