[SERVER-65819] Update existing tenant migration retryable writes oplog before startFetchingTimestamp fetcher to support shard merge. Created: 20/Apr/22 Updated: 29/Oct/23 Resolved: 07/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: | Suganthi Mani | Assignee: | Mathis Bessa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | shard-merge-milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Server Serverless 2022-06-13, Server Serverless 2022-06-27, Server Serverless 2022-07-11 |
| Participants: |
| Description |
|
For multi-tenant migration, createRetryableWritesOplogFetchingPipelineForTenantMigrations() fetches only the oplog entries generated by retryable writes with ts < startFetchingTimestamp, specific to a given migrating tenantID. For shard merge protocol, we should fetch oplog entries generated by retryable writes with ts < startFetchingTimestamp for all tenants. |
| Comments |
| Comment by Githook User [ 07/Jul/22 ] |
|
Author: {'name': 'mathisbessamdb', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}Message: |