MongoDB - Defect ID: 399805
InitialSyncerResetsOptimesOnNewAttempt unit test should set optime before starting initial syncer

Info

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.

Top User Comments

xgen-internal-githook commented on Tue, 24 Apr 2018 15:33:19 +0000: Author: {'email': 'william.schultz@mongodb.com', 'username': 'will62794', 'name': 'William Schultz'} Message: SERVER-29949 Fix race condition in InitialSyncerResetsOptimes unit test (cherry picked from commit e0b06a9da3c0c6071f4e636f3c3ba3e8851c5db0) Branch: v3.4 https://github.com/mongodb/mongo/commit/5390e6754a7184a97025f8a600160b9ce4ee5698 xgen-internal-githook commented on Fri, 14 Jul 2017 20:19:02 +0000: Author: {u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'} Message: SERVER-29949 Fix race condition in InitialSyncerResetsOptimes unit test Branch: master https://github.com/mongodb/mongo/commit/e0b06a9da3c0c6071f4e636f3c3ba3e8851c5db0

Steps to Reproduce