Replica set architecture mental model in MongoDB - Mini Project: Build & Apply

Replica Set Architecture Mental Model

📖 Scenario: You are managing a MongoDB database for a small online store. To ensure the database stays available and safe even if one server goes down, you want to set up a replica set. A replica set is a group of MongoDB servers that keep copies of the same data. This way, if one server fails, another can take over without losing data.

🎯 Goal: Build a simple MongoDB replica set configuration with three members: one primary and two secondaries. This setup will help you understand how MongoDB replica sets work to keep data safe and available.

📋 What You'll Learn

Create a replica set configuration object named rsConfig with exactly three members.

Each member must have a unique _id and host string.

Set the replica set name to rs0 in the configuration.

Add a priority setting of 1 for the primary member and 0 for the secondary members.

💡 Why This Matters

🌍 Real World

Replica sets are used in real MongoDB deployments to provide high availability and data redundancy. This prevents downtime and data loss if a server crashes.

💼 Career

Understanding replica set architecture is essential for database administrators and backend developers working with MongoDB to ensure reliable and fault-tolerant applications.

1

Create the basic replica set configuration object

Create a variable called rsConfig and assign it an object with a _id property set to the string 'rs0' and an empty array property called members.

MongoDB

rsConfig = {
    "_id": "rs0",
    "members": []
}
# Your code here

Hint

Think of rsConfig as the main setup object for your replica set. It needs a name and a place to list the servers.

2

Add the primary member to the replica set

Add an object to the members array inside rsConfig with _id set to 0, host set to 'mongo1:27017', and priority set to 1.

MongoDB

rsConfig = {
    "_id": "rs0",
    "members": []
}
# Add the primary member object to rsConfig['members']

Hint

The primary member is the main server that accepts writes. It needs a higher priority.

3

Add two secondary members to the replica set

Add two more objects to the members array inside rsConfig. The first should have _id 1, host 'mongo2:27017', and priority 0. The second should have _id 2, host 'mongo3:27017', and priority 0.

MongoDB

rsConfig = {
    "_id": "rs0",
    "members": [
        {"_id": 0, "host": "mongo1:27017", "priority": 1}
    ]
}
# Add two secondary member objects to rsConfig['members']

Hint

Secondary members replicate data from the primary and have lower priority so they don't become primary unless needed.

4

Complete the replica set configuration

Ensure the rsConfig object is fully defined with _id as 'rs0' and the members array contains exactly three member objects with the correct _id, host, and priority values as specified.

MongoDB

rsConfig = {
    "_id": "rs0",
    "members": [
        {"_id": 0, "host": "mongo1:27017", "priority": 1},
        {"_id": 1, "host": "mongo2:27017", "priority": 0},
        {"_id": 2, "host": "mongo3:27017", "priority": 0}
    ]
}
# Verify the full replica set configuration is correct

Hint

Double-check all member details and the replica set name to complete the setup.

Practice

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

easy

A. To backup data manually every hour

B. To keep copies of data on multiple servers for safety and availability

C. To store data in different formats on the same server

D. To speed up queries by using multiple CPUs on one server

Solution

1. Step 1: Understand replica set function

   A replica set keeps copies of data on multiple servers to protect against failure.

2. Step 2: Compare options

   Only To keep copies of data on multiple servers for safety and availability describes this purpose correctly; others describe unrelated tasks.

3. Final Answer:

   To keep copies of data on multiple servers for safety and availability -> Option B

4. Quick Check:

   Replica set = data copies on servers [OK]

Hint: Replica sets = multiple copies for safety [OK]

Common Mistakes:

• Confusing replica sets with sharding
• Thinking replica sets speed up CPU usage
• Believing backups are manual in replica sets

2. Which of the following is the correct way MongoDB decides the primary in a replica set?

easy

A. MongoDB automatically elects a primary among members

B. The server with the most data becomes primary

C. The oldest server is always primary

D. The user manually sets the primary server

Solution

1. Step 1: Recall primary election process

   MongoDB automatically elects one server as primary to manage writes.

2. Step 2: Eliminate incorrect options

   Primary is not chosen by data size, age, or manual setting.

3. Final Answer:

   MongoDB automatically elects a primary among members -> Option A

4. Quick Check:

   Primary election = automatic [OK]

Hint: Primary is chosen automatically, not manually [OK]

Common Mistakes:

• Assuming user sets primary manually
• Thinking data size decides primary
• Believing oldest server is primary

3. Consider a replica set with one primary and two secondaries. If the primary goes down, what happens next?

medium

A. All secondaries become primary at the same time

B. The replica set stops working until the original primary returns

C. One of the secondaries is automatically elected as the new primary

D. The data is lost because there is no primary

Solution

1. Step 1: Understand failover in replica sets

   If the primary fails, MongoDB elects a new primary from secondaries automatically.

2. Step 2: Check other options

   Replica sets do not stop working, do not have multiple primaries, and do not lose data immediately.

3. Final Answer:

   One of the secondaries is automatically elected as the new primary -> Option C

4. Quick Check:

   Failover = automatic new primary [OK]

Hint: Primary failure triggers automatic new primary election [OK]

Common Mistakes:

• Thinking replica set stops on primary failure
• Believing multiple primaries exist simultaneously
• Assuming data loss happens immediately

4. You set up a replica set but notice writes are failing. Which of these could be the cause?

medium

A. All members are healthy and synced

B. The replica set has only one member

C. Secondary nodes are accepting writes

D. No primary is elected in the replica set

Solution

1. Step 1: Identify write requirements in replica sets

   Writes must go to the primary; if no primary exists, writes fail.

2. Step 2: Analyze options

   Healthy members or single member replica sets usually allow writes; secondaries do not accept writes.

3. Final Answer:

   No primary is elected in the replica set -> Option D

4. Quick Check:

   Writes need primary elected [OK]

Hint: Writes fail if no primary exists [OK]

Common Mistakes:

• Thinking secondaries accept writes
• Assuming single member replica set blocks writes
• Ignoring primary election status

5. You want to ensure your MongoDB replica set remains available even if two servers fail. What is the minimum number of members you should have in your replica set?

hard

A. 5 members

B. 4 members

C. 3 members

D. 6 members

Solution

1. Step 1: Understand majority voting in replica sets

   Replica sets use majority votes to elect primary; to tolerate 2 failures, majority must be > half of total members.

2. Step 2: Calculate minimum members

   With 5 members, majority is 3; losing 2 still leaves 3 members to form majority and keep primary.

3. Final Answer:

   5 members -> Option A

4. Quick Check:

   To survive 2 failures, need 5 members [OK]

Hint: Majority = more than half; 5 members survive 2 failures [OK]

Common Mistakes:

• Choosing 3 or 4 members which can't tolerate 2 failures
• Not considering majority voting
• Assuming even number members are better