Skip to content

Commit 73d8c19

Browse files
committed
Update source/tutorial/deploy-replica-set.txt
Really fixed the Requirements section to betterreflect the intent and agree with docs elsewhere.
1 parent e3306c0 commit 73d8c19

File tree

1 file changed

+9
-7
lines changed

1 file changed

+9
-7
lines changed

source/tutorial/deploy-replica-set.txt

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -27,13 +27,15 @@ deployments require no additional members or configuration.
2727
Requirements
2828
------------
2929

30-
A replica set requires two or more distinct systems so that each system can run its own
31-
instance of :program:`mongod`. This tutorial will deal with a 3 member set. For
32-
development systems you can run all three instances of the :program:`mongod` process on a
33-
local system. (e.g. a laptop) or within a virtual instance. For production
34-
environments, you should endeavor to maintain as much separation between the members as
35-
possible. For example, when using VMs in Production, each member should live on separate
36-
host servers, served by redundant power circuits, and with redundant network paths.
30+
Most replica sets are made up of two or more :program:`mongod` instances. This tutorial
31+
will deal with a 3 member set specifically. In a production environment, this would
32+
usually involve a deployment on 3 distinct systems so that each system can run its own
33+
instance of :program:`mongod`. For development systems you can run all three instances
34+
of the :program:`mongod` process on a local system. (e.g. a laptop) or within a virtual
35+
instance. For production environments, you should endeavor to maintain as much separation
36+
between the members as possible. For example, when using VMs in Production, each member
37+
should live on separate host servers, served by redundant power circuits, and with
38+
redundant network paths.
3739

3840
Procedure
3941
---------

0 commit comments

Comments
 (0)