InitialSyncerResetsOptimesOnNewAttempt unit test should set optime before starting initial syncer

XMLWordPrintableJSON

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

      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:
            Will Schultz
            Reporter:
            Will Schultz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: