-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
Repl 2020-09-07, Repl 2020-10-05, Repl 2020-11-16, Repl 2020-11-30, Repl 2021-01-11, Repl 2021-01-25, Repl 2021-02-08
1) TenantMigrationDonor::Instance should abort active index builds for the tenant with abort error code as "ErrorCodes::TenantMigrationInProgress" and wait for those index builds to complete after TenantMigrationDonor::Instance has transitioned to data sync phase and before sending the recipientSyncData cmd to recipient.
2) Donor trying to start any new index builds for a tenant after the TenantMigrationDonor::Instance has transitioned to data sync phase, should throw an error "ErrorCodes::TenantMigrationInProgress".
3) Parent thread ("createIndexes") user thread on receiving the error "ErrorCodes::TenantMigrationInProgress" should wait for the tenant migration to complete and the tenant migration decision (abort/commit) to be majority replicated on the donor replica set.
- depends on
-
SERVER-48860 Create migration oplog applier class
- Closed
- is depended on by
-
SERVER-50495 [passthrough suite] Make tenant_migration_jscore_passthrough simulate migrations that commit
- Closed
-
SERVER-50805 Test multi-key updates during a tenant migration
- Closed
- related to
-
SERVER-53552 Tenant migration donor should pass startMigrationDonorTimestamp info to recipient via recipientSyncData cmd
- Closed
-
SERVER-53553 Make tenant migration recipient to start cloning tenant data only after the donor node's lastCommittedOpTime is >= startMigrationDonorTimestamp
- Closed
-
SERVER-53685 Need to handle case of indexes being created on an empty collection when cloning starts.
- Closed
-
SERVER-54347 Allow createIndexes and dropIndexes during tenant migration oplog application.
- Closed