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

InitialSyncerResetsOptimesOnNewAttempt unit test should set optime before starting initial syncer

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Minor - P4 Minor - P4
    • 3.4.15, 3.5.11
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v3.4
    • 0

      This unit test has a slight race condition. It calls _setMyLastOptime after calling InitialSyncer::startup(). InitialSyncer::startup() schedules _startInitialSyncAttempt to be run immediately, and if that function gets run before _setMyLastOptime is called in the unit test, the assertion will fail. This can be fixed by setting the optime before the InitialSyncer is started.

            Assignee:
            william.schultz@mongodb.com William Schultz (Inactive)
            Reporter:
            william.schultz@mongodb.com William Schultz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: