[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: |
|
||||||||||||||||
| 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: (cherry picked from commit 6abc7924ef3781e58ab7f87373bf6983a7c617c0) |
| Comment by Githook User [ 17/Nov/16 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |