[SERVER-47449] Re-evaluate sync source after fetching each batch of oplog entries Created: 09/Apr/20 Updated: 29/Oct/23 Resolved: 08/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Xuerui Fa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Sprint: | Repl 2020-05-04, Repl 2020-05-18 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||
| Description |
|
Check if there is a significantly closer node at the end of processing each new batch of oplog entries fetched. If the node is in initial sync, it should not re-evaluate its sync source. The node will use ping times and the new changeSyncSourceThresholdMillis server parameter to determine if the node could switch from syncing from a node in a different data center to a node within the same data center. This check will be skipped if the current sync source’s ping time satisfies changeSyncSourceThresholdMillis. If changeSyncSourceThresholdMillis is set to 0, nodes should not re-evaluate their sync source. |
| Comments |
| Comment by Githook User [ 08/May/20 ] |
|
Author: {'name': 'Xuerui Fa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}Message: |