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

Disable OplogFetcher sync source re-evaluation during initial sync

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.4.2, 3.5.2
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2017-01-23
    • 0

    Description

      The OplogFetcher will terminate with an error if it decides that another sync source would be better than its current one. This causes initial sync to fail. Since initial sync does not allow for sync source changes, it should not check if there are better sync sources. If there is a problem on the sync source, it will manifest itself in the cloning phase as well, and cause a failure there.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-16441 syncSourceFeedback can spin, with network traffic, during reconfig

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

          Task - A task that needs to be done. SERVER-27231 add failpoint to turn off re-evaluating sync sources, for jstests that manipulate chaining

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

          Activity

            People

              benety.goh@mongodb.com Benety Goh
              judah.schvimer@mongodb.com Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: