Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-20153

ClusterFindInitialBatchSizeIsZero unit test case for the AsyncResultsMerger should not rely on callback execution order

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.8
    • Affects Version/s: None
    • Component/s: Querying, Sharding
    • None
    • Fully Compatible
    • ALL
    • QuInt 8 08/28/15

      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.

            Assignee:
            david.storch@mongodb.com David Storch
            Reporter:
            david.storch@mongodb.com David Storch
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: