[DOCS-15625] Clarify that shards should be deployed as replica sets in 3.6 onward Created: 12/Sep/22  Updated: 22/Jan/24

Status: Backlog
Project: Documentation
Component/s: manual, Server
Affects Version/s: 4.4.0, 5.0.0, 6.0.0, 6.1.0-rc0
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Chris Kelly Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: backlog, feature, replication, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-69517 moveChunk command fails with "Transac... Closed
Participants:
Days since reply: 1 year, 21 weeks, 2 days ago
Epic Link: DOCSP-11702

 Description   

On https://www.mongodb.com/docs/v4.4/core/sharded-cluster-components/#sharded-cluster-components we see (correctly) that:

A MongoDB sharded cluster consists of the following components:

  • shard: Each shard contains a subset of the sharded data. As of MongoDB 3.6, shards must be deployed as a replica set.

However on https://www.mongodb.com/docs/v4.4/sharding/#sharded-cluster we see:

A MongoDB sharded cluster consists of the following components:

  • shard: Each shard contains a subset of the sharded data. Each shard can be deployed as a replica set.

An issue came up in SERVER-69517 where a user brought up this inconsistency and how it can cause confusion. I'm not sure if there are other locations that should be updated, but we should have this note anywhere that setting up shards is mentioned:

  • As of MongoDB 3.6, shards must be deployed as a replica set.

Generated at Thu Feb 08 08:13:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.