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

Blacklist update_where.js from sharded concurrency suites with balancer on and no txn override

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.1, 4.3.1
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.2
    • Linked BF Score:
      0

      Description

      update_where.js test performs updates with multi=true, which are sent without shard versions outside of a transaction when they cannot target a single shard. This can lead to several known anomalies (see SERVER-20361), so until the behavior of multi writes against sharded collections is improved, this test should be blacklisted from the sharded with balancer concurrency suites. Notably multi writes do use shard versions in transactions, so this test does not need to be blacklisted in concurrency_sharded_multi_stmt_txn_with_balancer.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              cheahuychou.mao Cheahuychou Mao
              Reporter:
              jack.mulrow Jack Mulrow
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: