[SERVER-28677] InitialSyncer::_setup_inlock() should reset last applied and durable optimes. Created: 07/Apr/17  Updated: 08/Jan/19  Resolved: 08/Jun/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.4.4, 3.5.6
Fix Version/s: 3.4.7, 3.5.9

Type: Bug Priority: Major - P3
Reporter: Benety Goh Assignee: William Schultz (Inactive)
Resolution: Done Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-29436 InitialSyncer doesn't need to update ... Backlog
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Repl 2017-05-08, Repl 2017-05-29, Repl 2017-06-19
Participants:
Case:
Linked BF Score: 0

 Description   

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



 Comments   
Comment by Githook User [ 27/Jun/17 ]

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

Comment by Githook User [ 08/Jun/17 ]

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

Comment by Spencer Brody (Inactive) [ 07/Apr/17 ]

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.

Generated at Thu Feb 08 04:18:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.