From e485c0dd9852fabbfb3078f2bd48d9c85f612bf7 Mon Sep 17 00:00:00 2001 From: dstolfo Date: Mon, 15 Apr 2013 15:13:38 -0400 Subject: [PATCH] Clarification of replica set sizes --- source/tutorial/deploy-replica-set.txt | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/source/tutorial/deploy-replica-set.txt b/source/tutorial/deploy-replica-set.txt index a222b5cf242..254eda1b15f 100644 --- a/source/tutorial/deploy-replica-set.txt +++ b/source/tutorial/deploy-replica-set.txt @@ -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 @@ -41,6 +41,8 @@ redundant network paths. ` 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 ` member. Procedures ----------