Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

6 Easy Steps to Configure MongoDB Replication Set

DZone's Guide to

6 Easy Steps to Configure MongoDB Replication Set

· Java Zone ·
Free Resource

FlexNet Code Aware, a free scan tool for developers. Scan Java, NuGet, and NPM packages for open source security and open source license compliance issues.

In this tutorial we'll create a 3-node cluster, where the first serves as a primary node, the second as a failover node, and the third as an Arbiter.

1. Setup Mongo and Set a Configuration File

In all the 3 servers adjust the configuration file /etc/mongod.conf:

#Select your replication set name
replSet=[replication_set_name]
#Select the replication log size
oplogSize=1024
Disable the bind_ip parameter to avoid binding to only 127.0.0.1 interface
#bind_ip

2. Restart All 3 mongod Daemons

 > sudo service mongod restart

3. Create an Initial Configuration on the Primary

Login to the primary mongo and create an initial configuration. Please notice to use the private IP and not the loopback address (127.0.0.1):

> mongo
Primary> cfg = {"_id" : "[replication_set_name]", "members" : [{"_id" : 0,"host" : "[Primary_Host_IP]:27017"}]}
Primary> rs.initiate(cfg);

4. Add the Failover Instance to the Replication Set

 Primary> rs.add("[Failover_Host_IP]:27017")

5. Add the Arbier Instance to the Replication Set

 Primary>rs.addArb(":27017")

6. Verify the Replication Set Status

 Primary>rs.status()

Bottom Line

I wish every data cluster setup was as easy as a setup of a MongoDB replication set.

Keep Performing, [a href="https://www.linkedin.com/in/moshekaplan" target="_blank"]Moshe Kaplan

 Scan Java, NuGet, and NPM packages for open source security and license compliance issues. 

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}