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

Race in AsyncResultsMerger error handling may trigger mongos invariant

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.4.1
    • Fix Version/s: 3.2.14, 3.4.4, 3.5.3
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.4, v3.2
    • Steps To Reproduce:
      Hide

      I was not able to reproduce so far.

      Show
      I was not able to reproduce so far.
    • Sprint:
      Query 2017-02-13
    • Case:
    • Linked BF Score:
      0

      Description

      We were running a stress test on a distributed sharded cluster (8 shards, 7 replicas, on 5 AWS regions), checking behaviour when killing different parts of the cluster.

      We setup 5 application servers (1 per region) with mongos on the same server.

      One of the mongos from where we were running the tests crashed after we killed some processes (including some config servers).

      The message when crashing was :
      Invariant failure remote.status.isOK() src/mongo/s/query/async_results_merger.cpp 345

      Attached is the mongos log.

      Tests started at 15:47 after sharding the collection "renault"

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: