[SERVER-86147] Handle cluster to cluster migrations (such as tenant migrations / shard merge / split etc.) when recordIdsReplicated:true Created: 02/Feb/24 Updated: 06/Feb/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Vishnu Kaushik | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
Tenant migrations and the other migrations listed above happen via the recipient primary, which means that as the data is copied over the recipient primary inserts it. As long as the recipient primary knows that the collection being copied has recordIdsReplicated:true (which may be something we need to implement - the primary probably won't know this), then from that point onward replication will ensure that the recordIds are the same (thanks to SERVER-78348 / SERVER-86046). However, the recordIds will NOT be the same as the recordIds on the source cluster, which should be OK. |