[SERVER-67954] Notify BackgroundSync when data relevant to sync source selection has changed Created: 11/Jul/22 Updated: 29/Oct/23 Resolved: 16/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Matthew Russotto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2022-07-25 |
| Participants: |
| Description |
|
If BackgroundSync does not find a suitable sync source, it will wait for 1 second before trying again to find one. In some cases, the replication system knows conditions relevant to sync source selection have changed; for instance, another node has changed member state (heartbeat) or advanced its optime (heartbeat or replSetUpdatePosition). In these cases, the 1 second wait should be interrupted to allow faster sync source selection and resumption of replication. |
| Comments |
| Comment by Githook User [ 16/Jul/22 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |
| Comment by Githook User [ 16/Jul/22 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |