[SERVER-50908] Investigate if ShardNotFound special-case handling in migration recovery can be avoided Created: 14/Sep/20  Updated: 26/Oct/23

Status: Backlog
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Kevin Pulo Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-46202 Implement ShardRegistry on top of Rea... Closed
Assigned Teams:
Catalog and Routing
Participants:

 Description   

In the ShardRegistry rewrite on SERVER-46202, it was necessary to add special-case handling for ShardNotFound errors to migration recovery (here and here, for when the recipient shard has been removed). We should investigate if it's possible to rework this interaction so that this special case isn't needed.


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