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

Blacklist queryoptimizer3.js from all sharding passthrough suites

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.6.0-rc1
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2017-10-23
    • 0

    Description

      queryoptimizer3.js has a parallel thread running periodic drop collection commands. The rest of the test is performing reads and further drops. In the sharding suites, this test keeps running into LockBusy. This is because the cluster drop collection command takes distlocks, whereas the shard drop collection command does not.

      Some of the failing suites: causally_consistent_jscore_passthrough_WT, sharding_jscore_passthrough_WT, sharding_jscore_op_query_passthrough_WT, sharding_jscore_passthrough_wire_ops_WT, concurrency_sharded_causal_consistency_and_balancer, sharded_collections_jscore_passthrough_WT

      Attachments

        Issue Links

          Activity

            People

              dianna.hohensee@mongodb.com Dianna Hohensee
              dianna.hohensee@mongodb.com Dianna Hohensee
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: