[SERVER-15905] Ensure Initial Sync uses the same source when fetching oplog + missing docs Created: 31/Oct/14 Updated: 24/Jun/19 Resolved: 24/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.6.5, 2.7.8 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Judah Schvimer |
| Resolution: | Done | Votes: | 0 |
| Labels: | datarepl3.2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Sprint: | Repl 2019-07-15 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Now that initial sync uses bgsync, and a sep. oplog reader from the applier, we should ensure it is not possible for them to be out of sync when fetching missed document. See sync.cpp:72 – this should use the bgsync oplog reader source. |
| Comments |
| Comment by Judah Schvimer [ 24/Jun/19 ] |
|
This is done here and the source is used here. Closing "Gone Away". |
| Comment by Judah Schvimer [ 14/Jun/19 ] |
|
I'm pretty sure this is "Gone Away". Have to confirm. |
| Comment by Spencer Brody (Inactive) [ 04/Nov/14 ] |
|
Realized there were possible problems if the sync source changes or becomes empty b/c there is no valid sync source. Bumping out of 2.7 release until we can come up with a more comprehensive solution to this problem |
| Comment by Githook User [ 04/Nov/14 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: Revert " This reverts commit d204985463cd731d16190fd79621e227850d9c84. |
| Comment by Githook User [ 03/Nov/14 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |