[SERVER-27079] DataReplicator should wait for last oplog fetcher to finish before starting next initial sync attempt Created: 16/Nov/16  Updated: 05/Apr/17  Resolved: 17/Nov/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.4.0-rc3
Fix Version/s: 3.4.2, 3.5.1

Type: Bug Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-27098 review and fix log levels in DataRepl... Closed
is depended on by SERVER-27052 Add asynchronous operation support to... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.4
Sprint: Repl 2016-11-21
Participants:
Linked BF Score: 0

 Description   

DataReplicator::_anyActiveHandles_inlock() and DataReplicator::_waitOnAndResetAll_inlock() are not checking _lastOplogFetcher. This may cause delayed _lastOplogFetcher callbacks to run during the next initial sync attempt.



 Comments   
Comment by Githook User [ 22/Dec/16 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-27079 DataReplicator should wait for last oplog fetcher to finish before starting next initial sync attempt

(cherry picked from commit 6abc7924ef3781e58ab7f87373bf6983a7c617c0)
Branch: v3.4
https://github.com/mongodb/mongo/commit/05c812f26b9652077bc0f7d5a12048cc5357dc3f

Comment by Githook User [ 17/Nov/16 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-27079 DataReplicator should wait for last oplog fetcher to finish before starting next initial sync attempt
Branch: master
https://github.com/mongodb/mongo/commit/6abc7924ef3781e58ab7f87373bf6983a7c617c0

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