[DOCS-10874] Deploy a Sharded Cluster page should mention replica set names requirement Created: 06/Oct/17  Updated: 30/Oct/23  Resolved: 12/Feb/18

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Major - P3
Reporter: Kevin Adistambha Assignee: Brian Moss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 6 years, 1 week, 2 days ago

 Description   

The Deploy a Sharded Cluster page is missing one crucial information regarding deploying a CSRS sharded cluster: the replica set names for the config replica set and each of the shard replica set should be different. Otherwise, adding shards would fail at the later steps with:

{
  "code": 20,
  "ok": 0,
  "errmsg": "A shard already exists containing the replica set 'replicaset'"
}

Suggestion: Add the naming restriction wordings (possibly inside a green "Note" box) under:



 Comments   
Comment by Githook User [ 05/Feb/18 ]

Author:

{'email': 'kallimachos@gmail.com', 'name': 'Brian Moss', 'username': 'kallimachos'}

Message: DOCS-10874 Mention replica set names requirement
Branch: v3.2
https://github.com/mongodb/docs/commit/5d5b2aff2f2324342db1ed15ebee7bf7bc4e6bb2

Comment by Githook User [ 05/Feb/18 ]

Author:

{'email': 'kallimachos@gmail.com', 'name': 'Brian Moss', 'username': 'kallimachos'}

Message: DOCS-10874 Mention replica set names requirement
Branch: v3.4
https://github.com/mongodb/docs/commit/32923fd23ae76e7ccc53998d843c1faac97a36b9

Comment by Githook User [ 05/Feb/18 ]

Author:

{'email': 'kallimachos@gmail.com', 'name': 'Brian Moss', 'username': 'kallimachos'}

Message: DOCS-10874 Mention replica set names requirement
Branch: master
https://github.com/mongodb/docs/commit/0fceb2e5c118956616998a6b2b437c1b369ac57d

Comment by David McKay [ 01/Feb/18 ]

Just got caught out by this. Should definitely be mentioned in the docs.

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