[SERVER-10844] Single shard queries can be optimized (sort/skip) Created: 23/Sep/13 Updated: 28/May/19 Resolved: 12/Jun/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.7.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | ning | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 1 |
| Labels: | pull-request | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
on sharding cluster , if:
mongos will ask mongod to reply all the matched records, and do skip on mongos. which is not efficient because no INDEX is used. and too much data is transfer between mongod and mongos see this explain:
we can just pass the query to the shard like what we did on not-sharded collection. |
| Comments |
| Comment by Githook User [ 12/Jun/14 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: Also removes dead code, add comments from parallel.cpp. Based on changes from idning <idning@gmail.com> |
| Comment by Greg Studer [ 23/May/14 ] |
|
Moved into 2.7.2. |
| Comment by ning [ 19/Nov/13 ] |
|
how's the Code Review? |