-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Distributed Query Planning
-
None
-
Query Integration
-
Fully Compatible
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
Currently, the RoutingContext performs validation in its destructor that all namespaces have had their routing tables validated by sending a request and receiving a response from a shard. We log an error message if validation did not complete upon termination. This should be strengthened (i.e. to a tassert) in test builds, and ideally moved out of the destructor so that it doesn't crash the entire process.
- is depended on by
-
SERVER-102925 Replace direct CatalogCache accesses in the sharded aggregation code with the RoutingContext
-
- In Progress
-
-
SERVER-104395 Replace getCollectionRoutingInfoForTxnCmd with RoutingContext
-
- In Progress
-
-
SERVER-104721 Use withValidatedRoutingContext helper in routing operations that call the RoutingContext
-
- Closed
-
- is related to
-
SERVER-102928 Validate the RoutingContext before termination
-
- Closed
-
- related to
-
SERVER-104795 ShardSvrDropIndexes() should not skip validated shards on retries during concurrent chunk migrations
-
- Closed
-