MongoDB - Defect ID: 371985
InitialSyncer::_setup_inlock() should reset last applied and durable optimes.

Info

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

Top User Comments

xgen-internal-githook commented on Tue, 27 Jun 2017 20:10:58 +0000: Author: {u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'} Message: SERVER-28677 InitialSyncer should reset optimes on every attempt (cherry picked from commit 1c56f5dd262111f921203d403f54fedb18772792) Branch: v3.4 https://github.com/mongodb/mongo/commit/d915259708b79fd7394aa8de9779520710d2bbe7 xgen-internal-githook commented on Thu, 8 Jun 2017 22:21:51 +0000: Author: {u'username': u'will62794', u'name': u'William Schultz', u'email': u'william.schultz@mongodb.com'} Message: SERVER-28677 InitialSyncer should reset optimes on every attempt Branch: master https://github.com/mongodb/mongo/commit/1c56f5dd262111f921203d403f54fedb18772792 spencer commented on Fri, 7 Apr 2017 22:06:29 +0000: According to benety.goh, the impact of this is that the server crashes. But it should not result in any data corruption or incorrect write acknowledgement.

Steps to Reproduce