-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
Repl 2021-02-08, Repl 2021-02-22
startMigrationDonorTimestamp indicates that the recipient should start cloning/fetching tenant data from donor only after that timestamp. This ticket should address 2 things.
1) Add a new field "startMigrationDonorTimestamp" in recipientSyncData cmd
2) Tenant migration donor would set the startMigrationDonorTimestamp to donor lastAppliedTimestamp (which is >= donor initial state doc write timestamp)
- is depended on by
-
SERVER-50495 [passthrough suite] Make tenant_migration_jscore_passthrough simulate migrations that commit
- Closed
-
SERVER-53553 Make tenant migration recipient to start cloning tenant data only after the donor node's lastCommittedOpTime is >= startMigrationDonorTimestamp
- Closed
- is related to
-
SERVER-48862 Donor should not be able to start/commit a index build for a tenant at a timestamp >= recipientSyncData cmd's startMigrationDonorTimestamp
- Closed