[SERVER-20153] ClusterFindInitialBatchSizeIsZero unit test case for the AsyncResultsMerger should not rely on callback execution order Created: 26/Aug/15 Updated: 19/Sep/15 Resolved: 27/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.8 |
| Type: | Bug | 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 | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | QuInt 8 08/28/15 | ||||||||
| Participants: | |||||||||
| Description |
|
The test case creates an AsyncResultsMerger backed by a TaskExecutor with a mock network interface. The ARM has three remote nodes, which each return a batch of zero results in response to the initial find command. The processing of each of these batches happens in a TaskExecutor callback, and these callbacks may execute in any order. The test, however, assumes that the callbacks run in a specific order. |
| Comments |
| Comment by Githook User [ 27/Aug/15 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: |