Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
Fully Compatible
-
Repl 2021-02-22
Description
As part of this ticket, we need to do 2 things
1) Tenant migration recipient should persist the startMigrationDonorTimestamp by writing it to the tenant migration recipient instance's state document.
2) TenantMigrationRecipientService::Instance::_getStartOpTimesFromDonor() will send find commands with afterClusterTimestamp set as startMigrationDonorTimestamp and with readConcern:kMajority. That will make sure that the majority reads (for collection cloning and oplog fetching) by the recipient on the donor will be made only after startMigrationDonorTimestamp.
Attachments
Issue Links
- depends on
-
SERVER-53552 Tenant migration donor should pass startMigrationDonorTimestamp info to recipient via recipientSyncData cmd
-
- Closed
-
- is depended on by
-
SERVER-50495 [passthrough suite] Make tenant_migration_jscore_passthrough simulate migrations that commit
-
- Closed
-
-
SERVER-54449 Enable index related tests in tenant_migration_jscore_passthrough suite
-
- 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
-