-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2020-11-02, Sharding 2021-03-22, Sharding 2021-04-05, Sharding 2021-04-19
-
2
Focus on using AsyncTry pattern to handle recovery for donor shards.
List of things to consider:
- Whether we need to consider kError as a special case during processing resharding fields. It's possible that the processing logic won't have yet known whether a donor/recipient document has been written.
- depends on
-
SERVER-49894 Have resharding oplog fetcher resume from 'ts' component of largest _id inserted
- Closed
-
SERVER-52693 Have ReshardingCollectionCloner retry cloning on retryable errors from the donor shards
- Closed
-
SERVER-52922 Have config.transactions cloner for resharding resume from its progress lsid
- Closed
- related to
-
SERVER-55511 Handle recovery for resharding recipients
- Closed
-
SERVER-57195 Convert resharding document deletion to use PersistentTaskStore instead of creating a WriteUnitOfWork
- Closed