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).
- is depended on by
-
SERVER-32672 Standalone replica set shards reject requests with gossiped clusterTime from non __system users
- Closed
-
SERVER-33444 Investigate the remaining tests that fail when shard servers are started as replica sets
- Closed
- is related to
-
SERVER-32529 Requiring replSet for shards breaks Queryable Backup
- Closed
-
SERVER-32051 Require shard servers and config servers to be replica sets
- Closed
-
SERVER-32105 Require shard servers and config servers to be started with --replSet or 'replSetName'
- Closed
-
SERVER-32531 Require --shardsvrs not started in queryable backup mode to be started as replica sets
- Closed
-
SERVER-27342 Do not block unnecessarily on connecting to mongod or finishing initiate in ReplSetTest and ShardingTest
- Closed
- related to
-
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
- Closed
-
SERVER-33180 Update 2_test_launching_cluster.js test to use replica set shards
- Closed
-
SERVER-33597 Make allow_partial_results.js, return_partial_shards_down.js start shards as replica sets
- Closed
-
SERVER-33601 Make sharding_migrate_large_docs.js, bulk_insert.js, and prefix_shard_key.js start shards as replica sets
- Closed