Primary and secondary nodes in MongoDB - Mini Project: Build & Apply

Understanding Primary and Secondary Nodes in MongoDB Replica Set

📖 Scenario: You are managing a MongoDB replica set for a small online store. The replica set has one primary node and two secondary nodes. You want to understand how to identify the primary and secondary nodes using MongoDB queries.

🎯 Goal: Learn to query the replica set status to find which node is primary and which are secondary nodes.

📋 What You'll Learn

Create a variable called replicaSetStatus that stores the output of rs.status().

Create a variable called primaryNode to store the primary node's name from replicaSetStatus.

Create a list called secondaryNodes that contains the names of all secondary nodes from replicaSetStatus.

Add a final statement to show the replica set members with their roles.

💡 Why This Matters

🌍 Real World

Replica sets in MongoDB provide high availability and data redundancy. Knowing how to identify primary and secondary nodes helps in monitoring and managing the database cluster.

💼 Career

Database administrators and backend developers often need to check replica set status to troubleshoot issues or optimize read/write operations.

1

Get Replica Set Status

Create a variable called replicaSetStatus and assign it the result of rs.status() to get the current status of the replica set.

MongoDB

# Create a variable called replicaSetStatus and assign rs.status() to it
# Your code here

Hint

Use rs.status() to get the replica set status and assign it to replicaSetStatus.

2

Identify the Primary Node

Create a variable called primaryNode and assign it the name of the member whose stateStr is "PRIMARY" from replicaSetStatus.members.

MongoDB

replicaSetStatus = rs.status()
# Find the primary node's name and assign it to primaryNode
# Your code here

Hint

Use a generator expression to find the member with stateStr equal to "PRIMARY".

3

List All Secondary Nodes

Create a list called secondaryNodes that contains the name of all members whose stateStr is "SECONDARY" from replicaSetStatus.members.

MongoDB

replicaSetStatus = rs.status()
primaryNode = next(member['name'] for member in replicaSetStatus['members'] if member['stateStr'] == 'PRIMARY')
# Create a list of secondary node names called secondaryNodes
# Your code here

Hint

Use a list comprehension to collect all members with stateStr equal to "SECONDARY".

4

Show Replica Set Members and Roles

Create a variable called membersWithRoles that is a list of dictionaries. Each dictionary should have keys name and role, where role is the stateStr of the member from replicaSetStatus.members.

MongoDB

replicaSetStatus = rs.status()
primaryNode = next(member['name'] for member in replicaSetStatus['members'] if member['stateStr'] == 'PRIMARY')
secondaryNodes = [member['name'] for member in replicaSetStatus['members'] if member['stateStr'] == 'SECONDARY']
# Create a list of dictionaries called membersWithRoles with keys 'name' and 'role'
# Your code here

Hint

Use a list comprehension to create dictionaries with name and role for each member.

Practice

1. Which statement best describes the role of a primary node in a MongoDB replica set?

easy

A. It acts as a backup and does not participate in replication.

B. It only reads data and never accepts writes.

C. It accepts write operations and replicates data to secondary nodes.

D. It is used only for analytics and reporting.

Solution

1. Step 1: Understand the primary node's function

   The primary node is the main server that accepts all write operations in a replica set.

2. Step 2: Role in replication

   The primary replicates data changes to secondary nodes to keep data consistent.

3. Final Answer:

   It accepts write operations and replicates data to secondary nodes. -> Option C

4. Quick Check:

   Primary node = accepts writes and replicates [OK]

Hint: Primary node handles writes; secondaries replicate [OK]

Common Mistakes:

• Thinking primary only reads data
• Confusing secondary with primary roles
• Assuming primary is just a backup

2. Which of the following is the correct command to check the status of a MongoDB replica set?

easy

A. replica.status()

B. db.replicaStatus()

C. show replicaSet

D. rs.status()

Solution

1. Step 1: Recall MongoDB replica set commands

   The command rs.status() is used to check the status of the replica set.

2. Step 2: Verify other options

   Other options are not valid MongoDB shell commands for replica set status.

3. Final Answer:

   rs.status() -> Option D

4. Quick Check:

   Replica set status command = rs.status() [OK]

Hint: Use rs.status() to check replica set health [OK]

Common Mistakes:

• Using incorrect or non-existent commands
• Confusing database commands with replica set commands
• Typing commands with wrong syntax

3. Given a replica set with one primary and two secondary nodes, what will happen if the primary node goes down?

medium

A. The replica set will stop all read and write operations immediately.

B. One of the secondary nodes will be elected as the new primary.

C. The primary node will automatically restart without intervention.

D. All secondary nodes will become primary nodes simultaneously.

Solution

1. Step 1: Understand replica set failover

   If the primary node fails, the replica set automatically elects a new primary from the secondaries.

2. Step 2: Check other options

   The replica set does not stop all operations; it does not restart primary automatically; multiple primaries cannot exist simultaneously.

3. Final Answer:

   One of the secondary nodes will be elected as the new primary. -> Option B

4. Quick Check:

   Failover elects new primary from secondaries [OK]

Hint: Replica sets auto-elect new primary if current fails [OK]

Common Mistakes:

• Thinking all nodes become primary
• Assuming system stops all operations
• Believing primary restarts automatically

4. You run rs.stepDown() on the primary node but get an error saying "not primary". What is the likely cause?

medium

A. The node is already a secondary, not primary.

B. The command syntax is incorrect.

C. The replica set has only one node.

D. The network connection to the primary is lost.

Solution

1. Step 1: Understand rs.stepDown() usage

   This command only works on a primary node to force it to step down.

2. Step 2: Analyze the error message

   "not primary" means the node is already a secondary, so it cannot step down.

3. Final Answer:

   The node is already a secondary, not primary. -> Option A

4. Quick Check:

   rs.stepDown() error "not primary" = node is secondary [OK]

Hint: rs.stepDown() only works on primary nodes [OK]

Common Mistakes:

• Trying to step down a secondary node
• Assuming syntax error causes this message
• Ignoring the node's current role

5. You want to configure a MongoDB replica set with one primary and two secondaries. Which of the following configurations ensures data safety and availability during a primary failure?

hard

A. Set all nodes with priority 1 and enable majority write concern.

B. Set one secondary with priority 0 and disable write concern.

C. Use only one node as primary without secondaries.

D. Set all nodes with priority 0 to prevent elections.

Solution

1. Step 1: Understand priority and write concern

   Setting all nodes with priority 1 allows any secondary to become primary if needed. Majority write concern ensures writes are acknowledged by most nodes.

2. Step 2: Evaluate other options

   Priority 0 disables election for that node; disabling write concern risks data loss; single node has no failover; priority 0 on all nodes prevents elections.

3. Final Answer:

   Set all nodes with priority 1 and enable majority write concern. -> Option A

4. Quick Check:

   Priority 1 + majority write concern = safe failover [OK]

Hint: Use priority 1 and majority write concern for safety [OK]

Common Mistakes:

• Disabling write concern risking data loss
• Setting priority 0 disables elections
• Using single node without replicas