-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Security 2020-10-19, Sharding 2020-11-02
Store the largest _id value from the oplog entries applied from that donor shard in the config.localReshardingOperations.recipient.progress_applier document as the <progress {clusterTime, ts}> for that donor shard.
{ _id: <donor's shard ID>, progress: <donor1's progress {clusterTime, ts}>, }
The largest _id value from the oplog entries applied from that donor shard should be used with {$match: {_id: {$gt: <progress {clusterTime, ts}>}}} to resume.
When the donor shard's final oplog entry marker is applied, the config.localReshardingOperations.recipient.progress_applier document can be updated to store {_id: MaxKey} as an indicator that resuming is no longer necessary.
- related to
-
SERVER-49900 Update config.localReshardingOperations.recipient.progress_txn_cloner document following each batch of config.transactions cloner
- Closed
-
SERVER-50964 Create temporary swappable promise construct in order to receive messages on the RecipientStateMachine
- Closed