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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.1.8
    • Component/s: Querying, Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      QuInt 8 08/28/15

      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.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: