[SERVER-49186] Make donor's "data sync" function do the "start blocking" write Created: 30/Jun/20  Updated: 27/Jul/20  Resolved: 27/Jul/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Cheahuychou Mao
Resolution: Duplicate Votes: 0
Labels: pm-1791_milestone-A
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-48939 Make reads call MigratingTenantAccess... Closed
duplicates SERVER-49180 Make the donor's dataSync function re... Closed
Sprint: Sharding 2020-07-27, Sharding 2020-08-10
Participants:

 Description   

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."


Generated at Thu Feb 08 05:19:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.