[SERVER-51606] Handle recovery from resharding donors Created: 14/Oct/20  Updated: 29/Oct/23  Resolved: 08/Apr/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: Haley Connelly
Resolution: Fixed Votes: 0
Labels: PM-234-M3, PM-234-T-lifecycle
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-49894 Have resharding oplog fetcher resume ... Closed
depends on SERVER-52693 Have ReshardingCollectionCloner retry... Closed
depends on SERVER-52922 Have config.transactions cloner for r... Closed
Related
related to SERVER-55511 Handle recovery for resharding recipi... Closed
related to SERVER-57195 Convert resharding document deletion ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-11-02, Sharding 2021-03-22, Sharding 2021-04-05, Sharding 2021-04-19
Participants:
Story Points: 2

 Description   

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.


 Comments   
Comment by Githook User [ 08/Apr/21 ]

Author:

{'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}

Message: SERVER-51606 Handle recovery from resharding donors
Branch: master
https://github.com/mongodb/mongo/commit/60f2db4bd2f1bad10f1c92f3eb0b626eca933477

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