Automatic failover behavior in MongoDB - Mini Project: Build & Apply

Automatic Failover Behavior in MongoDB Replica Set

📖 Scenario: You are managing a MongoDB replica set for a small online store. The replica set has one primary and two secondary nodes. You want to understand how automatic failover works when the primary node goes down.

🎯 Goal: Build a simple MongoDB replica set configuration and simulate the automatic failover behavior by identifying the primary and secondaries, then observing the election process.

📋 What You'll Learn

Create a replica set configuration document named rsConfig with three members having IDs 0, 1, and 2

Add a variable primaryId set to 0 representing the current primary member

Write a query to find the current primary member from rsConfig.members using primaryId

Add a final step to update primaryId to 1 simulating failover to a new primary

💡 Why This Matters

🌍 Real World

Replica sets in MongoDB provide high availability by automatically electing a new primary if the current one fails, ensuring your application stays online.

💼 Career

Understanding automatic failover is essential for database administrators and backend developers to maintain reliable and fault-tolerant database systems.

1

Create the replica set configuration

Create a variable called rsConfig that is a dictionary with a key members containing a list of three dictionaries. Each dictionary should have keys _id with values 0, 1, and 2 respectively, and host with values "mongo0:27017", "mongo1:27017", and "mongo2:27017" respectively.

MongoDB

# Your code here

Need a hint?

Define rsConfig as a dictionary with a members list containing three member dictionaries with the specified _id and host values.

2

Set the current primary member ID

Create a variable called primaryId and set it to 0 to represent the current primary member in the replica set.

MongoDB

rsConfig = {
    "members": [
        {"_id": 0, "host": "mongo0:27017"},
        {"_id": 1, "host": "mongo1:27017"},
        {"_id": 2, "host": "mongo2:27017"}
    ]
}
# Your code here

Need a hint?

Set primaryId to 0 to indicate the first member is the primary.

3

Find the current primary member

Write a line of code to create a variable called primaryMember that finds the dictionary in rsConfig["members"] where the _id equals primaryId.

MongoDB

rsConfig = {
    "members": [
        {"_id": 0, "host": "mongo0:27017"},
        {"_id": 1, "host": "mongo1:27017"},
        {"_id": 2, "host": "mongo2:27017"}
    ]
}

primaryId = 0
# Your code here

Need a hint?

Use a generator expression with next() to find the member with _id equal to primaryId.

4

Simulate failover by changing the primary

Update the variable primaryId to 1 to simulate the automatic failover where the second member becomes the new primary.

MongoDB

rsConfig = {
    "members": [
        {"_id": 0, "host": "mongo0:27017"},
        {"_id": 1, "host": "mongo1:27017"},
        {"_id": 2, "host": "mongo2:27017"}
    ]
}

primaryId = 0

primaryMember = next(member for member in rsConfig["members"] if member["_id"] == primaryId)
# Your code here

Need a hint?

Change primaryId to 1 to simulate the failover to the second member.