-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Catalog and Routing
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.
- related to
-
SERVER-46202 Implement ShardRegistry on top of ReadThroughCache to make it causally consistent
- Closed