Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.0.0-rc0
Affects Version/s: None
Component/s: Sharding
Labels:
- PM-234-M3
- PM-234-T-lifecycle

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2020-11-02, Sharding 2021-03-22, Sharding 2021-04-05, Sharding 2021-04-19
Story Points:
2
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: Haley Connelly
Reporter:: Blake Oler
Participants:: Blake Oler, Githook User, Haley Connelly
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Oct 14 2020 08:23:37 PM UTC
Updated:: Oct 29 2023 10:01:56 PM UTC
Resolved:: Apr 08 2021 05:36:35 PM UTC
Confidence Status Last Update:: 11/Mar/21 7:04 PM