[DOCS-15126] [Server] REP-33: Conflict Resolution during Sharded Cluster Replication Created: 23/Feb/22 Updated: 13/Nov/23 Resolved: 06/Jul/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Dave Cuthbert (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 1 year, 50 weeks ago | ||||
| Epic Link: | DOCSP-21764 | ||||
| Description |
|
Original Downstream Change Summary This project adds some metadata collections in the users databases. These collections will be cleaned up if user commits migration properly, otherwise user will need to manually clean up these collections. Description of Linked TicketEpic Summary SummarySupport Conflict Resolution during Sharded Cluster Replication due to concurrent document movement between source shards MotivationAs in the proposed architecture for Cluster to Cluster Replication, when the source cluster is a sharded cluster, we would want to establish per-shard change streams via the source mongos(es). And if we want to increase parallelism and apply change events from different shards concurrently, we may get out-of-order (conflict) change events if a document is moved between shards (e.g. by a chunk migration). This project is to implement the solution identified in PM-2416 on top of REP-32 to handle such out-of-order (conflict) change events and support sharded clusters for C2C Replication with concurrent document movement between source shards. Cast of Characters
DocumentationProduct Description |