- 
    Type:Bug 
- 
    Resolution: Unresolved
- 
    Priority:Major - P3 
- 
    None
- 
    Affects Version/s: 5.0.7
- 
    Component/s: None
- 
        Query Integration
- 
        ALL
- 
        
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
Sharding a time series collection leads to higher throughput on write, but reads affect the whole cluster, because the primary shard has a spike in CPU usage. When reviewing the logs of Mongos, several log entries state that Resolved views on sharded collections must be executed by mongos. When I stop the read load, these messages are no longer logged.
From my research, it seems like this can be related to SERVER-43376 - Operations on non-sharded views in sharded clusters extra round trip
This is a problem for us, because adding a read load affects the whole cluster's performance. Our workload has about 25% reads for every 100% of writes.
I found the problem while load testing my sharded time series prototype on Atlas
- is related to
- 
                    SERVER-57437 Implement insert routing for sharded time series collection -         
- Closed
 
-         
- 
                    SERVER-42282 Consider replacing CommandOnShardedViewNotSupportedOnMongod mechanism with rewrite / routing from shard -         
- Backlog
 
-         













