-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Integration
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
This "isSharded" check is redundant: _generateIndexesIfNeeded is only ever called after _shardCollectionIfNeeded, which should have sharded the collection. Although this node's CatalogCache might now be stale, whenever it later dispatches the createIndexes cmd the shard will reject the request and inform the router that it is stale. It can be safely removed.
- is related to
-
SERVER-57519 Make ARS use causally consistent ShardRegistry::getShard() function
-
- Closed
-
-
SERVER-61214 Ensure having the latest known entry of the catalog cache when creating config.system.sessions
-
- Closed
-
-
SERVER-104020 Migrate scatterGatherVersionedTargetByRoutingTable functions to take in RoutingContext instead of CRI
-
- In Code Review
-
- related to
-
SERVER-61214 Ensure having the latest known entry of the catalog cache when creating config.system.sessions
-
- Closed
-