-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Fully Compatible
-
Server Serverless 2022-09-05
-
15
When a shard split recipient applies the recipient config locally, it should also reset the lastCommittedOpTime to the blockTimestamp. We will need to get the blockTimestamp from somewhere, current ideas are:
- Query the TenantMigrationAccessBlockerRegistry for shard split access blockers (they can gain an accessor for their blockTimestamp)
- Query the shardSplitDonors namespace for any documents representing an active shard split, and read the value directly from the state document
- related to
-
SERVER-67247 Cleanly split recipient nodes from donor set in a deterministic fashion for shard split
- Closed