-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Sharding 2020-07-27, Sharding 2020-08-10
After the "data sync" function adds the MigratingTenantAccessBlocker to MigratingTenantAccessBlockerByPrefix, it should update the donor's state machine doc's "state" to "blocking".
For now, the update can be done using DBDirectClient, see example.
(SERVER-49180 will modify the update so that it is done at a reserved OpTime and also sets "blockTimestamp" to the reserved OpTime's Timestamp.)
Add a jstest that calling donorStartMigration causes the state machine doc's "state" to get updated to "blocking."
- duplicates
-
SERVER-48939 Make reads call MigratingTenantAccessBlocker::checkIfCanReadOrBlock
- Closed
-
SERVER-49180 Make the donor's dataSync function reserve an OpTime at which to do the "start blocking" write
- Closed