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

Run the concurrency suite with shard stepdowns

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v3.6
    • Sprint:
      Sharding 2017-10-02, Sharding 2017-10-23, Sharding 2017-11-13, Sharding 2017-12-04, Sharding 2018-01-01, Sharding 2018-01-15, Sharding 2017-12-18
    • Linked BF Score:
      0

      Description

      Update the jstests/concurrency/fsm_all_sharded_with_stepdowns.js and jstests/concurrency/fsm_all_sharded_with_stepdowns_and_balancer.js files to specify

      {
        sharded: {enabled: true, stepdownOptions: {configStepdown: true, shardStepdown: true}},
        replication: {enabled: true}
      }
      

      as the cluster options. Since mongos won't automatically retry any operations destined for the shards, we'll want to additionally load() the jstests/libs/override_methods/auto_retry_on_network_error.js override from SERVER-30953 when shardStepdown=true inside of worker_thread.js similar to what's done for implicitly retrying on "DatabaseDropPending" error responses.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jack.mulrow Jack Mulrow
              Reporter:
              max.hirschhorn Max Hirschhorn
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: