[SERVER-27397] Disable OplogFetcher sync source re-evaluation during initial sync Created: 13/Dec/16  Updated: 05/Apr/17  Resolved: 18/Jan/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.4.2, 3.5.2

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer 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
Related
is related to SERVER-16441 syncSourceFeedback can spin, with net... Closed
is related to SERVER-27231 add failpoint to turn off re-evaluati... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Repl 2017-01-23
Participants:
Linked BF Score: 0

 Description   

The OplogFetcher will terminate with an error if it decides that another sync source would be better than its current one. This causes initial sync to fail. Since initial sync does not allow for sync source changes, it should not check if there are better sync sources. If there is a problem on the sync source, it will manifest itself in the cloning phase as well, and cause a failure there.



 Comments   
Comment by Githook User [ 22/Jan/17 ]

Author:

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

Message: SERVER-27397 disable OplogFetcher sync source re-evaluation during initial sync

(cherry picked from commit 4b35e713718e1d0f44dae516726b173c150efcef)
Branch: v3.4
https://github.com/mongodb/mongo/commit/68eb7dad8c49e9d379860452e7ee583a393435d8

Comment by Githook User [ 18/Jan/17 ]

Author:

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

Message: SERVER-27397 disable OplogFetcher sync source re-evaluation during initial sync
Branch: master
https://github.com/mongodb/mongo/commit/4b35e713718e1d0f44dae516726b173c150efcef

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