-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2026-06-08, CAR Team 2026-06-22
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When we throw staleConfig, we should generally have access to the sharding state since the shardId in the error represents the shard throwing the error. We should update these places to generate a stale config exception containing a shard ref, with a UUID when present. This will also require updating handlers of stale config exceptions to be okay with this change.
- is related to
-
SERVER-131597 [master] Revert SERVER-128164
-
- Closed
-