Skip to content

DOCSP-5991 clarify that use of multiple replica sets require multiple… #5457

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions source/includes/fact-unique-replica-set-names.rst
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
If your application connects to more than one replica set, each set
should have a distinct name. Some drivers group replica set
connections by replica set name.
If your application connects to more than one replica set, each set must
have a distinct name. Some drivers group replica set connections by
replica set name.
8 changes: 4 additions & 4 deletions source/includes/steps-deploy-replica-set.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -10,12 +10,12 @@ content: |
For each member, start a :binary:`~bin.mongod` instance with the
following settings:

- Set :setting:`replication.replSetName` option to the replica set name,

.. include:: /includes/fact-unique-replica-set-names.rst
- Set :setting:`replication.replSetName` option to the replica set
name. If your application connects to more than one replica set,
each set must have a distinct name.

- Set :setting:`net.bindIp` option to the hostname/ip or a comma-delimited
list of hostnames/ips, and
list of hostnames/ips.

- Set any other settings as appropriate for your deployment.

Expand Down