-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Optimization
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
When a read against a non-materialized view is performed in a sharded cluster, the read is first sent to the primary shard for the database, which then looks up the view definition and returns to mongos as part of a CommandOnShardedViewNotSupportedOnMongod error response. We could consider instead performing the rewrite locally on the primary shard and then performing shard to shard routing. This would save us a network hop from the primary shard back to mongos.
- is related to
-
-
- Closed
-
- related to
-
SERVER-65949 Sharded time series leads to high query rates on the primary shard with CommandOnShardedViewNotSupportedOnMongod errors
-
- Blocked
-
-
-
- Closed
-