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

Shard by thread id in update_upsert_multi fsm workloads

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.7
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 2019-01-28

      Description

      The two update_upsert_multi.js concurrency workloads are blacklisted from all sharded suites because they perform multi updates without the shard key. The updates from all workloads do include the thread id, so if the collections used by each workload is sharded by thread id instead of defaulting to _id, both workloads should be able to run against sharded clusters. 

        Attachments

          Activity

            People

            Assignee:
            jack.mulrow Jack Mulrow
            Reporter:
            jack.mulrow Jack Mulrow
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: