From e3306c0abcab48fc2b32429f93e384288a0fa092 Mon Sep 17 00:00:00 2001 From: Adam C Date: Fri, 4 Jan 2013 01:03:18 +0000 Subject: [PATCH 1/2] Update source/tutorial/deploy-replica-set.txt Fixed the requirements section to agree with the docs here: http://docs.mongodb.org/manual/core/replication/ The requirement for a set is two or more, but the tutorial describes three, and it led to some confusion in the community: http://serverfault.com/questions/462780/does-a-mongodb-replica-set-require-at-least-2-or-3-members --- source/tutorial/deploy-replica-set.txt | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/source/tutorial/deploy-replica-set.txt b/source/tutorial/deploy-replica-set.txt index 610d1e77ebf..8e9180920ba 100644 --- a/source/tutorial/deploy-replica-set.txt +++ b/source/tutorial/deploy-replica-set.txt @@ -27,14 +27,13 @@ deployments require no additional members or configuration. Requirements ------------ -A replica set requires three distinct systems so that each system can run its own instance -of :program:`mongod`. For development systems you can run all three -instances of the :program:`mongod` process on a local system. (e.g. a -laptop) or within a virtual instance. For production environments, you -should endeavor to maintain as much separation between the members as possible. For -example, when using VMs in Production, each member should live on -separate host servers, served by redundant power circuits, and with -redundant network paths. +A replica set requires two or more distinct systems so that each system can run its own +instance of :program:`mongod`. This tutorial will deal with a 3 member set. For +development systems you can run all three instances of the :program:`mongod` process on a +local system. (e.g. a laptop) or within a virtual instance. For production +environments, you should endeavor to maintain as much separation between the members as +possible. For example, when using VMs in Production, each member should live on separate +host servers, served by redundant power circuits, and with redundant network paths. Procedure --------- From 73d8c199fec419190af858d28707b3c40cb861ee Mon Sep 17 00:00:00 2001 From: Adam C Date: Fri, 4 Jan 2013 01:19:08 +0000 Subject: [PATCH 2/2] Update source/tutorial/deploy-replica-set.txt Really fixed the Requirements section to betterreflect the intent and agree with docs elsewhere. --- source/tutorial/deploy-replica-set.txt | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/source/tutorial/deploy-replica-set.txt b/source/tutorial/deploy-replica-set.txt index 8e9180920ba..fcab0bf2ee3 100644 --- a/source/tutorial/deploy-replica-set.txt +++ b/source/tutorial/deploy-replica-set.txt @@ -27,13 +27,15 @@ deployments require no additional members or configuration. Requirements ------------ -A replica set requires two or more distinct systems so that each system can run its own -instance of :program:`mongod`. This tutorial will deal with a 3 member set. For -development systems you can run all three instances of the :program:`mongod` process on a -local system. (e.g. a laptop) or within a virtual instance. For production -environments, you should endeavor to maintain as much separation between the members as -possible. For example, when using VMs in Production, each member should live on separate -host servers, served by redundant power circuits, and with redundant network paths. +Most replica sets are made up of two or more :program:`mongod` instances. This tutorial +will deal with a 3 member set specifically. In a production environment, this would +usually involve a deployment on 3 distinct systems so that each system can run its own +instance of :program:`mongod`. For development systems you can run all three instances +of the :program:`mongod` process on a local system. (e.g. a laptop) or within a virtual +instance. For production environments, you should endeavor to maintain as much separation +between the members as possible. For example, when using VMs in Production, each member +should live on separate host servers, served by redundant power circuits, and with +redundant network paths. Procedure ---------