[DOCS-15441] Investigate changes in REP-784: PrimaryPreferred read preference on the destination can lead to regressing state Created: 23/Jun/22 Updated: 22/Jan/24 |
|
| Status: | Backlog |
| Project: | Documentation |
| Component/s: | C2C, manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | backlog, request | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 1 year, 32 weeks, 6 days ago | ||||
| Epic Link: | DOCSP-22764 | ||||
| Description |
|
Original Downstream Change Summary We modified the way we handle read preference in mongosync:
If the user reverses the replication direction, we will apply the same logic on the new source and new destination. e.g.
We may also see similar issues whenever we hit the api/v1/progress endpoint: it may return stale data. To solve this, we should: Moved part on linearizability to https://jira.mongodb.org/browse/REP-854 |