MongoDB is an open-source NoSQL database that stores data in a flexible document-based format. MongoDB replica sets provide data replication and help improve database availability by maintaining multiple copies of the data across different hosts.<\/p>\n\n\n\n
This guide explains how to install MongoDB on CentOS, configure replication, create a MongoDB cluster using a replica set, add an arbiter, and check the replication status using MongoDB commands.<\/p>\n\n\n\n
Before setting up the MongoDB cluster, make sure you have:<\/p>\n\n\n\n
sudo<\/code> access to the servers.<\/li>\n\n\n\n- Network connectivity between all MongoDB hosts.<\/li>\n\n\n\n
- Port
27017<\/code> accessible between the MongoDB servers.<\/li>\n\n\n\n- MongoDB installed on all hosts.<\/li>\n\n\n\n
- Hostnames or IP addresses of all MongoDB servers.<\/li>\n<\/ul>\n\n\n\n
Implementation<\/h2>\n\n\n\nStep 1: Create the MongoDB Repository<\/h3>\n\n\n\n
Create a repository file named mongodb-org-3.2.repo<\/code> under \/etc\/yum.repos.d\/<\/code> with the following content:<\/p>\n\n\n\n[mongodb-org-3.2]\nname=MongoDB Repository\nbaseurl=https:\/\/repo.mongodb.org\/yum\/redhat\/$releasever\/mongodb-org\/3.2\/x86_64\/\ngpgcheck=1\nenabled=1\ngpgkey=https:\/\/www.mongodb.org\/static\/pgp\/server-3.2.asc<\/pre>\n\n\n\nStep 2: Install MongoDB<\/h3>\n\n\n\n
Install the MongoDB server using yum<\/code>:<\/p>\n\n\n\nyum install -y mongodb-org<\/pre>\n\n\n\nStep 3: Modify the MongoDB Data Path<\/h3>\n\n\n\n
If you want to use a different location for storing MongoDB data, modify the dbPath<\/code> in \/etc\/mongodb.conf<\/code>.<\/p>\n\n\n\nFor example:<\/p>\n\n\n\n
dbPath: \/opt\/mongodata<\/pre>\n\n\n\nStep 4: Start the MongoDB Service<\/h3>\n\n\n\n
Start the MongoDB service:<\/p>\n\n\n\n
sudo service mongod start<\/pre>\n\n\n\nEnable MongoDB to start automatically after a server reboot:<\/p>\n\n\n\n
chkconfig mongod on<\/pre>\n\n\n\nStep 5: Configure the Bind IP<\/h3>\n\n\n\n
If MongoDB is accessed only locally, the existing bind IP configuration can be retained.<\/p>\n\n\n\n
If MongoDB needs to be accessed from remote servers, configure the bind IP appropriately in \/etc\/mongodb.conf<\/code>.<\/p>\n\n\n\nThe original configuration can be commented out:<\/p>\n\n\n\n
#bindIp:<\/pre>\n\n\n\n\nNote:<\/strong> If MongoDB is exposed to remote hosts, make sure firewall rules and authentication are properly configured. Avoid exposing MongoDB directly to the public internet.<\/p>\n<\/blockquote>\n\n\n\nFor additional MongoDB installation information, refer to the official MongoDB documentation.<\/p>\n\n\n\n
Setting Up MongoDB Cluster<\/h2>\n\n\n\nStep 1: Verify Connectivity Between Hosts<\/h3>\n\n\n\n
Make sure that all MongoDB hosts can communicate with each other over port 27017<\/code>.<\/p>\n\n\n\nThe MongoDB servers should be able to connect to one another before configuring replication.<\/p>\n\n\n\n
Step 2: Configure Replication<\/h3>\n\n\n\n
Modify \/etc\/mongodb.conf<\/code> on all MongoDB hosts<\/strong> and add the replication configuration:<\/p>\n\n\n\nreplication:\n replSetName: <replicationname><\/pre>\n\n\n\nUse the same replica set name on every MongoDB host.<\/p>\n\n\n\n
Step 3: Restart MongoDB<\/h3>\n\n\n\n
After updating the configuration, restart the MongoDB service on all hosts.<\/p>\n\n\n\n
sudo service mongod restart<\/pre>\n\n\n\nMake sure the service starts successfully on each server before continuing.<\/p>\n\n\n\n
Step 4: Initialize the Replica Set<\/h3>\n\n\n\n
On the primary host, open the MongoDB shell:<\/p>\n\n\n\n
mongo<\/pre>\n\n\n\nExecute the following configuration:<\/p>\n\n\n\n
conf = {\n _id: \"<replicationName>\",\n members:\n [\n {_id : 0, host : \"Host1IPAddress:27017\"},\n {_id : 1, host : \"Host2IPAddress:27017\"},\n {_id : 2, host : \"Host3IPAddress:27017\"}\n ]\n}<\/pre>\n\n\n\nInitialize the replica set:<\/p>\n\n\n\n
rs.initiate(conf)<\/pre>\n\n\n\nMongoDB will use the configured hosts as members of the replica set.<\/p>\n\n\n\n
Step 5: Check Replication Status<\/h3>\n\n\n\n
To verify the replica set status, execute:<\/p>\n\n\n\n
rs.status()<\/pre>\n\n\n\nThis command displays information about the replica set members and their current states.<\/p>\n\n\n\n
Adding a MongoDB Arbiter<\/h2>\n\n\n\n
MongoDB also supports an arbiter<\/strong>.<\/p>\n\n\n\nAn arbiter does not store a copy of the dataset and cannot become a primary. It can participate in elections by providing an additional vote for selecting the primary.<\/p>\n\n\n\n
Step 1: Remove the Host from the Existing Cluster<\/h3>\n\n\n\n
If the host is already part of the cluster, remove it first:<\/p>\n\n\n\n
rs.remove(\"HOSTIPADDRESS:27017\");<\/pre>\n\n\n\nStep 2: Add the Host as an Arbiter<\/h3>\n\n\n\n
From the primary replica set member, execute:<\/p>\n\n\n\n
rs.addArb(\"HOSTIPAddress:27017\");<\/pre>\n\n\n\nStep 3: Verify the Configuration<\/h3>\n\n\n\n
Check the replica set configuration:<\/p>\n\n\n\n
rs.conf()<\/pre>\n\n\n\nThe arbiter member should show:<\/p>\n\n\n\n
\"arbiterOnly\" : true<\/pre>\n\n\n\nBonus MongoDB Commands<\/h2>\n\n\n\nCheck Current Running Queries<\/h3>\n\n\n\n
To view currently running MongoDB operations:<\/p>\n\n\n\n
db.currentOp();<\/pre>\n\n\n\nMake the Primary Become Secondary<\/h3>\n\n\n\n
To step down the current primary:<\/p>\n\n\n\n
rs.stepDown(300)<\/pre>\n\n\n\nThis allows another eligible replica set member to become primary.<\/p>\n\n\n\n
Check Replication Status<\/h3>\n\n\n\n
Use:<\/p>\n\n\n\n
rs.status()<\/pre>\n\n\n\nCheck Whether the Host Is Primary<\/h3>\n\n\n\n
Use:<\/p>\n\n\n\n
db.isMaster()<\/pre>\n\n\n\nThis command can be used to check the role\/status of the MongoDB server.<\/p>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
Setting up a MongoDB replica set allows MongoDB data to be replicated across multiple servers and provides better availability. By configuring the same replica set name on each host, adding the required members, and initialisingTalk to our experts<\/p>\n\n\n\n
Looking for the right technology solution for your business? Our team of experts can help you with development, cloud, DevOps, design, and a wide range of other technology needs. Get in touch with our team here<\/a>. the replica set, you can create a basic MongoDB cluster.<\/p>\n\n\n\nMongoDB arbiters can also be used when an additional voting member is required without maintaining another copy of the dataset. Commands such as rs.status()<\/code>, rs.conf()<\/code>, and db.currentOp()<\/code> help administrators monitor and manage the MongoDB environment.<\/p>\n\n\n\nFAQs<\/h2>\n\n\n\n1. What is a MongoDB replica set?<\/h3>\n\n\n\n
A MongoDB replica set is a group of MongoDB instances that maintain copies of the same dataset and work together to provide replication and high availability.<\/p>\n\n\n\n
2. Which port does MongoDB use by default?<\/h3>\n\n\n\n
MongoDB uses port 27017<\/strong> by default. All replica set members should be able to communicate with each other over this port.<\/p>\n\n\n\n3. What is a MongoDB arbiter?<\/h3>\n\n\n\n
An arbiter is a MongoDB replica set member that does not store data. It participates in elections by providing a voting member without maintaining a copy of the dataset.<\/p>\n\n\n\n
4. How can I check the MongoDB replica set status?<\/h3>\n\n\n\n
Run the following command from the MongoDB shell:<\/p>\n\n\n\n
rs.status()<\/pre>\n\n\n\n5. How can I check the replica set configuration?<\/h3>\n\n\n\n
Use:<\/p>\n\n\n\n
rs.conf()<\/pre>\n\n\n\nThis displays the configuration and members of the replica set, including whether a member is configured as an arbiter.<\/p>\n\n\n\n
Related Articles<\/h2>\n\n\n\n\n- Using GraphQL to Create Blogs with Image Uploads in MongoDB<\/strong> \u2013 Learn how to use GraphQL with MongoDB to build a blog application and handle image uploads.
Read the article<\/a><\/li>\n\n\n\n- Data Types and Data Model in MongoDB<\/strong> \u2013 Understand MongoDB data types and the fundamentals of designing data models for MongoDB applications.
Read the article<\/a><\/li>\n<\/ul>\n\n\n\nTalk to our experts.<\/h2>\n\n\n\n