Skip to content

Clarification of replica set sizes #859

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.

Sign up for GitHub

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
wants to merge 1 commit into from
Closed

Clarification of replica set sizes #859

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 4 additions & 2 deletions source/tutorial/deploy-replica-set.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,8 +25,8 @@ deployments require no additional members or configuration.
Requirements
------------

Most replica sets consist of two or more :program:`mongod`
instances. [#odd-numbered-set-sizes]_ This tutorial
Most replica sets consist of three or more :program:`mongod`
instances. [#odd-numbered-set-sizes]_ [#two-member-replica-set]_ This tutorial
describes a three member set. Production environments should have at
least three distinct systems so that each system can run its own
instance of :program:`mongod`. For development systems you can run all three instances
Expand All @@ -41,6 +41,8 @@ redundant network paths.
<replica-set-elections>` always design replica sets with odd numbers
of members. Use :ref:`replica-set-arbiters` to ensure the set has
odd number of voting members and avoid tied elections.
.. [#two-member-replica-set] A two member replica set can exist provided
that one of the members of the set is a :ref:`hidden <replica-set-hidden-members>` member.

Procedures
----------
Expand Down