[SERVER-18767] Make find command shard version aware Created: 01/Jun/15 Updated: 19/Sep/15 Resolved: 31/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Quint Iteration 7, Quint 9 09/18/15 | ||||||||
| Participants: | |||||||||
| Comments |
| Comment by Githook User [ 31/Aug/15 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: |
| Comment by Githook User [ 06/Aug/15 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: |
| Comment by David Storch [ 28/Jul/15 ] |
|
The AsyncResultsMerger can't signal that results are available until it has the first batch from each remote node because if a late-responding node indicates stale shard version, all results so far have to be thrown out. The query then has to be re-targeted and retried. |
| Comment by David Storch [ 09/Jul/15 ] |
|
Work under this ticket should also include stale config handling in the find/getMore commands on mongos. |