Skip to content

Commit 3c766f2

Browse files
ajhuh-mdbandf-mongodb
authored andcommitted
DOCSP-5991 clarify that use of multiple replica sets require multiple client objects
1 parent d58bb6a commit 3c766f2

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed
Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
1-
If your application connects to more than one replica set, each set
2-
should have a distinct name. Some drivers group replica set
3-
connections by replica set name.
1+
If your application connects to more than one replica set, each set must
2+
have a distinct name. Some drivers group replica set connections by
3+
replica set name.

source/includes/steps-deploy-replica-set.yaml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,12 +10,12 @@ content: |
1010
For each member, start a :binary:`~bin.mongod` instance with the
1111
following settings:
1212
13-
- Set :setting:`replication.replSetName` option to the replica set name,
14-
15-
.. include:: /includes/fact-unique-replica-set-names.rst
13+
- Set :setting:`replication.replSetName` option to the replica set
14+
name. If your application connects to more than one replica set,
15+
each set must have a distinct name.
1616
1717
- Set :setting:`net.bindIp` option to the hostname/ip or a comma-delimited
18-
list of hostnames/ips, and
18+
list of hostnames/ips.
1919
2020
- Set any other settings as appropriate for your deployment.
2121

0 commit comments

Comments
 (0)