-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
Sharding 2021-02-22, Sharding 2021-03-08
Create the TenantMigrationAccessBlocker after cloning in the TenantMigrationRecipientService, move it to the unblocked state after the recipient has applied data past the returnAfterReachingDonorTimestamp (blockTimestamp).
- depends on
-
SERVER-53581 Extend TenantMigrationAccessBlocker to block reads on recipient
- Closed
-
SERVER-54653 Make ContinuousTenantMigration hook garbage collect each migration before starting the next one
- Closed
- is depended on by
-
SERVER-53583 Advance rejectReadsBeforeTimestamp when receiving a new recipientSyncData command
- Closed
-
SERVER-53584 Create recipient TenantMigrationAccessBlockers on startup, initial sync and rollback
- Closed
- is duplicated by
-
SERVER-53585 Remove recipient TenantMigrationAccessBlockers when state machine is removed
- Closed
- is related to
-
SERVER-53768 Block TTL deletions on tenant being migrated on recipient until the migration is forgotten
- Closed