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

Update ShardingTest to default to starting shard servers as single-node replica sets rather than standalones

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.7.3
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2018-01-15, Sharding 2018-02-12, Sharding 2018-02-26, Sharding 2018-03-12

    Description

      Since shard servers are required to be replica sets as of 3.6 (SERVER-32051), we should update our test infrastructure to always start shards as replica sets.

      Note: Ensure that doing so does not significantly increase test run times (does not cause suites to time out on Evergreen).

      Attachments

        Issue Links

          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-32672 Standalone replica set shards reject requests with gossiped clusterTime from non __system users

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-33444 Investigate the remaining tests that fail when shard servers are started as replica sets

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-32529 Requiring replSet for shards breaks Queryable Backup

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. SERVER-32051 Require shard servers and config servers to be replica sets

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-32105 Require shard servers and config servers to be started with --replSet or 'replSetName'

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-32531 Require --shardsvrs not started in queryable backup mode to be started as replica sets

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-27342 Do not block unnecessarily on connecting to mongod or finishing initiate in ReplSetTest and ShardingTest

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-33599 Out collection not in UUID catalog when shards started as replica sets in mapReduce_outSharded.js, mrShardedOutput.js, forget_mr_temp_ns.js

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-33180 Update 2_test_launching_cluster.js test to use replica set shards

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-33597 Make allow_partial_results.js, return_partial_shards_down.js start shards as replica sets

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-33601 Make sharding_migrate_large_docs.js, bulk_insert.js, and prefix_shard_key.js start shards as replica sets

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              janna.golden@mongodb.com Janna Golden
              esha.maharishi@mongodb.com Esha Maharishi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: