Skip to content

Update source/tutorial/deploy-replica-set.txt #509

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

Merged
merged 2 commits into from
Jan 4, 2013
Merged
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
15 changes: 8 additions & 7 deletions source/tutorial/deploy-replica-set.txt
Original file line number Diff line number Diff line change
Expand Up @@ -27,13 +27,14 @@ 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
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
Expand Down