[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:
Related
is related to SERVER-20186 ClusterClientCursor needs to include ... Closed
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: SERVER-18767 fix bug preventing mongod from using the ShardFilterStage for the find command
Branch: master
https://github.com/mongodb/mongo/commit/0c53d176ec23277606fe96c31cf914523f92e1e7

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: SERVER-18767 make find command shard version aware
Branch: master
https://github.com/mongodb/mongo/commit/1d2a75a01acd26de9969b1e980e301401120ed10

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.

Generated at Thu Feb 08 03:48:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.