Skip to content

Commit 0fceb2e

Browse files
kallimachoskay-kim
authored andcommitted
DOCS-10874 Mention replica set names requirement
1 parent 5073287 commit 0fceb2e

File tree

1 file changed

+19
-9
lines changed

1 file changed

+19
-9
lines changed

source/tutorial/deploy-shard-cluster.txt

Lines changed: 19 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,8 @@ Overview
2020
This tutorial involves creating a new sharded cluster that consists of a
2121
:binary:`~bin.mongos`, the config server replica set, and two shard replica sets.
2222

23-
For instructions specific to sharding a collection, see
24-
:ref:`deploy-hashed-sharded-cluster-shard-collection` or
23+
For instructions specific to sharding a collection, see
24+
:ref:`deploy-hashed-sharded-cluster-shard-collection` or
2525
:ref:`deploy-ranged-sharded-cluster-shard-collection`.
2626

2727
Considerations
@@ -30,9 +30,9 @@ Considerations
3030
Connectivity
3131
~~~~~~~~~~~~
3232

33-
Each member of a sharded cluster must be able to connect to *all* other
34-
members in the cluster. This includes all shards and config servers.
35-
Ensure that network and security systems, including all interface and
33+
Each member of a sharded cluster must be able to connect to *all* other
34+
members in the cluster. This includes all shards and config servers.
35+
Ensure that network and security systems, including all interface and
3636
firewalls, allow these connections.
3737

3838
CloudManager and OpsManager
@@ -80,9 +80,9 @@ For details on using x.509 for client authentication, see
8080
Host Identifier
8181
~~~~~~~~~~~~~~~
8282

83-
If you use either ``localhost`` or ``127.0.0.1`` as the hostname portion of
84-
any host identifier, you *must* use that identifier as the host setting
85-
for any other MongoDB component in the cluster.
83+
If you use either ``localhost`` or ``127.0.0.1`` as the hostname portion of
84+
any host identifier, you *must* use that identifier as the host setting
85+
for any other MongoDB component in the cluster.
8686

8787
For example, the :method:`sh.addShard()` method takes a ``host`` parameter for
8888
the hostname of the target shard. If you set ``host`` to ``localhost``, you
@@ -105,6 +105,11 @@ For a production deployment, deploy a config server replica set with at
105105
least three members. For testing purposes, you can create a
106106
single-member replica set.
107107

108+
.. note::
109+
110+
The config server replica set must not use the same name as any of the
111+
shard replica sets.
112+
108113
.. include:: /includes/steps/deploy-sharded-cluster-config-server-noauth.rst
109114

110115
Once the config server replica set (CSRS) is initiated and up, proceed
@@ -117,6 +122,11 @@ For a production deployment, use a replica set with at least three
117122
members. For testing purposes, you can create a single-member replica
118123
set.
119124

125+
.. note::
126+
127+
Shard replica sets must not use the same name as the config server replica
128+
set.
129+
120130
.. include:: /includes/steps/deploy-sharded-cluster-shard-replica-noauth.rst
121131

122132
.. _sharding-setup-start-mongos:
@@ -181,7 +191,7 @@ Shard a Collection
181191

182192
This section contains an overall description of the sharding process.
183193

184-
For instructions specific to :ref:`sharding-ranged` sharding,
194+
For instructions specific to :ref:`sharding-ranged` sharding,
185195
see :ref:`deploy-ranged-sharded-cluster-shard-collection`.
186196

187197
For instructions specific to :ref:`sharding-hashed` sharding,

0 commit comments

Comments
 (0)