-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 3.2.0, 3.4.0, 3.6.0, 4.0.0
-
Component/s: Querying
-
Minor Change
-
Query 2019-12-16, Query 2019-12-30, Query 2020-01-13
-
(copied to CRM)
-
0
It looks like when SERVER-19355 was implemented the logic for handling sort/skip/limit that gets sent to shards gets sent to primary shard for queries on unsharded collections as well.
This results in mongod returning more documents to mongos and mongos then applying the skip rather than mongod just returning only the required data to mongos (after applying the skip and limit).
Not sure if this is a bug or just a missed opportunity for optimization.
- is duplicated by
-
SERVER-41329 Improve skip performance in mongos when request is sent to a single shard
- Closed
- related to
-
SERVER-41329 Improve skip performance in mongos when request is sent to a single shard
- Closed