Replica set configuration basics in MongoDB - Mini Project: Build & Apply

Replica set configuration basics

📖 Scenario: You are setting up a MongoDB replica set to ensure your database stays available even if one server goes down. A replica set is a group of MongoDB servers that keep the same data, so if one fails, another can take over.

🎯 Goal: Create a basic MongoDB replica set configuration with three members. You will define the replica set configuration document step-by-step, including the replica set name and the members with their IDs and hostnames.

📋 What You'll Learn

Create a variable called rsConfig to hold the replica set configuration document.

Add a _id field to rsConfig with the value "rs0" as the replica set name.

Add a members array to rsConfig with three members, each having an _id and host.

Add a priority field to the first member to make it the primary candidate.

💡 Why This Matters

🌍 Real World

Replica sets are used in MongoDB to provide high availability and data redundancy. Setting up the configuration correctly is essential for production databases.

💼 Career

Database administrators and backend engineers often configure replica sets to ensure database reliability and uptime.

1

Create the initial replica set configuration object

Create a variable called rsConfig and assign it an object with a single field _id set to the string "rs0".

MongoDB

// Create the replica set configuration object with _id 'rs0'
// Your code here

Hint

The replica set configuration must have an _id field that names the replica set.

2

Add members array with three members

Add a members field to the rsConfig object. It should be an array with three objects. Each object must have an _id (0, 1, 2) and a host string: "mongo0:27017", "mongo1:27017", and "mongo2:27017" respectively.

MongoDB

var rsConfig = { _id: "rs0" };
// Add members array with three members to rsConfig
// Your code here

Hint

The members field is an array of objects. Each member needs a unique _id and a host string with hostname and port.

3

Set priority for the first member

Add a priority field with value 2 to the first member object in the members array inside rsConfig. This makes it the preferred primary.

MongoDB

var rsConfig = {
  _id: "rs0",
  members: [
    { _id: 0, host: "mongo0:27017" },
    { _id: 1, host: "mongo1:27017" },
    { _id: 2, host: "mongo2:27017" }
  ]
};
// Add priority: 2 to the first member
// Your code here

Hint

Set priority: 2 inside the first member object to make it the primary candidate.

4

Complete the replica set configuration

Ensure the rsConfig object is fully defined with _id as "rs0", a members array of three members with _id and host, and the first member has priority: 2.

MongoDB

var rsConfig = {
  _id: "rs0",
  members: [
    { _id: 0, host: "mongo0:27017", priority: 2 },
    { _id: 1, host: "mongo1:27017" },
    { _id: 2, host: "mongo2:27017" }
  ]
};
// Finalize the replica set configuration
// Your code here

Hint

Check that the entire rsConfig object is correctly structured as a replica set configuration.

Practice

1. What is the main purpose of a MongoDB replica set?

easy

A. To keep multiple copies of data for safety and availability

B. To speed up queries by using multiple CPUs

C. To store data in different formats

D. To backup data to an external server

Solution

1. Step 1: Understand what a replica set is

   A replica set is a group of MongoDB servers that keep copies of the same data.

2. Step 2: Identify the main goal of this setup

   The main goal is to keep data safe and available by having multiple copies.

3. Final Answer:

   To keep multiple copies of data for safety and availability -> Option A

4. Quick Check:

   Replica set purpose = data safety and availability [OK]

Hint: Replica sets keep data copies for safety and uptime [OK]

Common Mistakes:

• Thinking replica sets speed up queries directly
• Confusing replica sets with backups
• Assuming replica sets change data formats

2. Which command correctly initiates a replica set with one member named 'mongo1'?

easy

A. rs.start({ _id: 'rs0', members: ['mongo1'] })

B. rs.initiate({ _id: 'rs0', members: [{ _id: 0, host: 'mongo1:27017' }] })

C. replicaSet.create({ name: 'rs0', nodes: ['mongo1'] })

D. initReplicaSet({ id: 'rs0', hosts: ['mongo1:27017'] })

Solution

1. Step 1: Recall the correct syntax for initiating a replica set

   The command is rs.initiate() with a config object including _id and members array.

2. Step 2: Check the options for correct syntax and fields

   rs.initiate({ _id: 'rs0', members: [{ _id: 0, host: 'mongo1:27017' }] }) uses rs.initiate with _id and members array with _id and host fields correctly.

3. Final Answer:

   rs.initiate({ _id: 'rs0', members: [{ _id: 0, host: 'mongo1:27017' }] }) -> Option B

4. Quick Check:

   rs.initiate with config object = correct syntax [OK]

Hint: Use rs.initiate with _id and members array for setup [OK]

Common Mistakes:

• Using wrong command names like rs.start or initReplicaSet
• Passing members as simple strings instead of objects
• Missing port number in host field

3. Given this replica set config:

rs.initiate({ _id: 'rs0', members: [ { _id: 0, host: 'mongo1:27017' }, { _id: 1, host: 'mongo2:27017' } ] })

What will be the state of the second member immediately after initiation?

medium

A. ARBITER

B. SECONDARY

C. PRIMARY

D. STARTUP

Solution

1. Step 1: Understand member states after rs.initiate()

   After initiation, members start in STARTUP state before election completes.

2. Step 2: Identify the initial state of the second member

   The second member will be in STARTUP state until it syncs and elections finish.

3. Final Answer:

   STARTUP -> Option D

4. Quick Check:

   New members start as STARTUP before becoming SECONDARY [OK]

Hint: New members start in STARTUP state before election [OK]

Common Mistakes:

• Assuming member is immediately PRIMARY or SECONDARY
• Confusing ARBITER with normal members
• Ignoring the startup phase after initiation

4. You run rs.initiate() but get an error: "members array is missing or empty." What is the likely cause?

medium

A. You did not provide a members array in the config object

B. You used the wrong command name

C. You included an invalid port number

D. You forgot to start the mongod service

Solution

1. Step 1: Analyze the error message

   The error says the members array is missing or empty, meaning the config lacks members.

2. Step 2: Match error to common causes

   Not providing the members array in rs.initiate config causes this error.

3. Final Answer:

   You did not provide a members array in the config object -> Option A

4. Quick Check:

   Missing members array = error message [OK]

Hint: Always include members array in rs.initiate config [OK]

Common Mistakes:

• Ignoring the need for members array
• Assuming wrong command name causes this error
• Thinking service not started causes this error

5. You want to add a third member as an arbiter to your replica set. Which configuration snippet correctly adds it?

hard

A. { _id: 2, host: 'mongo3:27017', votes: 0 }

B. { _id: 2, host: 'mongo3:27017', priority: 2 }

C. { _id: 2, host: 'mongo3:27017', arbiterOnly: true }

D. { _id: 2, host: 'mongo3:27017', hidden: true }

Solution

1. Step 1: Understand arbiter configuration

   An arbiter member is configured with the field arbiterOnly set to true.

2. Step 2: Identify the correct option

   { _id: 2, host: 'mongo3:27017', arbiterOnly: true } sets arbiterOnly: true, which correctly marks the member as an arbiter.

3. Final Answer:

   { _id: 2, host: 'mongo3:27017', arbiterOnly: true } -> Option C

4. Quick Check:

   ArbiterOnly true = arbiter member [OK]

Hint: Use arbiterOnly: true to add an arbiter member [OK]

Common Mistakes:

• Using priority or votes fields incorrectly for arbiters
• Confusing hidden members with arbiters
• Not setting arbiterOnly to true for arbiters