Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Sharding
Labels:
None

Assigned Teams:

Sharding EMEA
Sprint:
Sharding EMEA 2021-06-28
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

(2 related to)

Assignee:: [DO NOT USE] Backlog - Sharding EMEA
Reporter:: Esha Maharishi (Inactive)
Participants:: [DO NOT USE] Backlog - Sharding EMEA, Esha Maharishi, Githook User, Kaloian Manassiev, Marcos José Grillo Ramirez
Votes:: 0 Vote for this issue
Watchers:: 10 Start watching this issue

Created:: Jan 03 2018 06:48:46 PM UTC
Updated:: Dec 06 2022 03:42:42 AM UTC
Resolved:: Jul 27 2021 04:19:23 PM UTC
Confidence Status Last Update:: 22/Jun/21 4:33 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates