-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Sharding EMEA
-
Sharding EMEA 2021-06-28
A commit to require --shardsvrs to be started as replica sets under SERVER-32105 went into 3.6.1, but was reverted because mongods started in queryable backup mode cannot be started as replica sets.
This ticket should re-commit the original patch, but allowing an --shardsvrs in queryable backup mode to be started as standalone servers.
- duplicates
-
SERVER-27383 Require --replSet with --configsvr
- Closed
- is duplicated by
-
SERVER-6621 mongos doesn't learn if a shard becomes a replica set after the mongos started up
- Closed
- is related to
-
SERVER-32529 Requiring replSet for shards breaks Queryable Backup
- Closed
-
SERVER-34121 "Cannot specify afterClusterTime readConcern without replication enabled"
- Closed
- related to
-
SERVER-32051 Require shard servers and config servers to be replica sets
- Closed
-
SERVER-32052 Update ShardingTest to default to starting shard servers as single-node replica sets rather than standalones
- Closed
-
SERVER-32105 Require shard servers and config servers to be started with --replSet or 'replSetName'
- Closed