[SERVER-22990] Ensure that sync source blacklisting doesn't delay rollbacks Created: 07/Mar/16 Updated: 06/Dec/22 Resolved: 20/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
Due to how the bgsync fetcher blacklists hosts when it returns OplogStartMissing before rollback, it may cause a rollback to be delayed later on when finding a start position or fetching the oplog. This may not be an issue in the new DataReplicator implementation but we should ensure so once it is completed. |