How to Configure MongoDB Replica Set on Linux

Edited 2 weeks ago by ExtremeHow Editorial Team

ConfigurationReplica SetLinuxMongoDBDatabaseSetupDevelopmentHigh AvailabilityClusterSynchronization

Creating a MongoDB replica set is an essential part of ensuring high availability and data redundancy in your applications that rely on MongoDB. In this guide, we will explain in detail how to configure a MongoDB replica set on a Linux-based system. This explanation will span across multiple topics, including understanding what a replica set is, prerequisites, installation, configuration, testing, and more. This detailed guide covers everything you need to know to set up a replica set from scratch in simple English.

Understanding MongoDB replica sets

Before delving into the technical configuration, it is important to understand what a MongoDB replica set is. A replica set in MongoDB is a group of MongoDB database nodes that maintain the same data set, thus providing data redundancy and high availability. A typical replica set consists of at least three instances or nodes of MongoDB:

• Primary node: It is the main node that receives all write operations.
• Secondary nodes: These nodes copy data from the primary and are capable of becoming the new primary in the event of a failover.
• Arbiter node (optional): This node exists to resolve differences in elections, but does not store data.

Replica sets allow seamless failover, meaning that if the primary node goes down, one of the secondaries can be promoted to primary, allowing your application to continue running with minimal interruption.

Prerequisites

To set up a MongoDB replica set, you need the following prerequisites:

• At least three Linux machines (physical or virtual), ideally in different locations for high availability.
• MongoDB is installed on all nodes. We will be using MongoDB Community Edition for this tutorial.
• Root or sudo privileges on all machines to install and configure MongoDB.
• To become familiar with basic Linux command line operations.
• Network connectivity between all MongoDB nodes.

Step-by-step guide to configuring MongoDB replica set

1. Install MongoDB on all nodes

The first step is to install MongoDB on all your Linux machines. Depending on your Linux distribution, the installation commands may vary.

For Ubuntu (using apt):

sudo apt update 
sudo apt install -y mongodb

For CentOS (using yum):

sudo yum install -y mongodb-org

Make sure MongoDB is running on each machine:

sudo systemctl start mongod 
sudo systemctl enable mongod

2. Configure each MongoDB instance

After MongoDB is installed and running on each node, you must configure each instance to be part of a replica set. Edit the MongoDB configuration file, typically found at /etc/mongod.conf, with your favorite text editor.

Locate the line that begins with replication: and set replSetName. Make sure the name is the same across all nodes in your replica set. Add or modify the section like this:

replication: 
  replSetName: "myReplicaSet"

Save and close the file. Then restart the MongoDB service on all nodes to apply the changes:

sudo systemctl restart mongod

3. Initialize the replica set

Now that the MongoDB instances are configured, go to the server you want to designate as primary.
Run the MongoDB shell:

mongo

In the MongoDB shell, use the following command to initialize the replica set:

rs.initiate()

The above command initiates the replica set on your primary server.

4. Add other nodes to the replica set

Once the replica set is initialized, you can add other nodes (secondaries, and optionally an arbiter) to the replica set using rs.add() command.

For example, to add a secondary node:

rs.add("hostname2:27017")

Replace hostname2:27017 with the actual address and port of the secondary node.

Repeat the process for additional secondary nodes, if available:

rs.add("hostname3:27017")

If you want to add an arbiter node:

rs.addArb("hostname4:27017")

5. Verify the replica set status

Check the status of the replica set by using the following command:

rs.status()

This command will provide a detailed report showing the status of each node in the replica set. Verify that each node is in the expected state (primary, secondary, arbiter).

Testing the replica set configuration

Once the replica set is configured, it is important to test its functionality to ensure that it behaves correctly during failures. Here are some tests you can perform:

Test 1: Primary Elections

Stop the MongoDB service on the current primary node:

sudo systemctl stop mongod

Check the replica set status on any secondary node:

mongo

Then run within the MongoDB shell:

rs.status()

Now one of the secondary nodes should become the new primary node. Restart MongoDB on the original primary node and verify that it has rejoined the replica set as a secondary node.

Test 2: Data Consistency

When the new primary node is selected, insert data into it and check if this data is replicated to the secondary nodes.

use testDB 
db.testCollection.insert({"name": "Replication Test"})

Then, check the presence of data on one of the secondary nodes by running the following:

rs.slaveOk() 
db.testCollection.find()

Test 3: Arbiter Functionality

In scenarios where you have an arbiter, you can test its functionality by intentionally stopping a node and verifying that the arbiter helps elect the new primary.

Stop and restart one of the secondary MongoDB services:

rs.status()

Make sure your arbiter is present and performs its role properly when a vote is necessary.

Troubleshooting common problems

Network configuration

Problems often arise due to improper network configuration; make sure all nodes can communicate with each other and all firewalls are configured to allow communication on port 27017 (or whatever port MongoDB is configured to use).

Access control

If authentication is enabled, make sure that you create the appropriate user roles and credentials that allow the nodes of the replica set to authenticate with each other.

Read and write concerns

Understand how MongoDB's read and write concern levels work so you can configure them to suit your application's needs, especially in replica set scenarios.

Conclusion

Configuring MongoDB replica sets on Linux systems is crucial for applications that require high availability and reliability. By following this comprehensive guide, you should be able to set up replica sets effectively, understanding the importance of each step. Running a replica set ensures that your data is replicated across multiple nodes, making your database system more fault-tolerant and well-equipped to handle real-world application demands.

Remember, always monitor the health and performance of your MongoDB replica set and adjust the configuration according to changing application requirements. With the right setup and maintenance, MongoDB replica sets can provide a robust database solution for mission-critical applications.

  Share This Article

If you find anything wrong with the article content, you can request an update