Automatic failover behavior in MongoDB - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is automatic failover in MongoDB?

Automatic failover is the process where MongoDB automatically switches to a new primary node if the current primary becomes unavailable, ensuring the database stays available without manual intervention.

beginner

What role does a 'primary' node play in MongoDB replica sets?

The primary node receives all write operations and replicates data to secondary nodes. It is the main point for data changes in the replica set.

intermediate

How does MongoDB detect a primary node failure?

MongoDB members send heartbeats to each other. If a majority of nodes do not receive a heartbeat from the primary within a timeout, they consider it down and start an election for a new primary.

intermediate

What is the election process in MongoDB automatic failover?

When the primary fails, eligible secondary nodes hold an election to select a new primary. The node that wins the majority vote becomes the new primary and starts accepting writes.

advanced

Why is a majority vote important in MongoDB failover?

A majority vote prevents split-brain scenarios by ensuring only one primary is elected. This keeps data consistent and avoids conflicts.

What triggers automatic failover in a MongoDB replica set?

A Primary node becomes unreachable

B Secondary node receives a write

C Client disconnects

D Backup completes

Automatic failover happens when the primary node is unreachable or considered down by the replica set members.

During failover, how is the new primary chosen?

A Node with the most data

B Majority vote among eligible secondaries

C Random selection

D Oldest node

Eligible secondary nodes hold an election and the one with majority votes becomes the new primary.

What is the purpose of heartbeat messages in MongoDB replica sets?

A To check node availability

B To backup data

C To transfer data

D To authenticate users

Heartbeat messages help nodes check if other members, especially the primary, are alive and reachable.

What happens if a majority of nodes cannot communicate with the primary?

A Primary remains primary

B Replica set shuts down

C An election is triggered to select a new primary

D All writes are blocked permanently

If the primary is unreachable by a majority, an election is triggered to maintain availability.

Why is it important to have an odd number of voting members in a replica set?

A To reduce storage

B To improve backup speed

C To increase write speed

D To simplify elections and avoid ties

An odd number of voting members helps avoid tie votes during elections, ensuring smooth failover.

Explain how MongoDB handles automatic failover when the primary node fails.

Think about how nodes communicate and decide who becomes the new leader.

Describe why majority voting is critical in MongoDB's automatic failover mechanism.

Consider what could happen if two primaries existed at the same time.

Practice

1. What is the main purpose of automatic failover in MongoDB replica sets?

easy

A. To backup data to an external storage device

B. To manually restart the database server when it crashes

C. To increase the speed of database queries

D. To switch to a backup server automatically if the primary server fails

Solution

1. Step 1: Understand automatic failover concept

   Automatic failover means the system switches servers without manual help when the main server fails.

2. Step 2: Identify the correct purpose in MongoDB context

   MongoDB replica sets use automatic failover to keep the database available by switching to a backup server automatically.

3. Final Answer:

   To switch to a backup server automatically if the primary server fails -> Option D

4. Quick Check:

   Automatic failover = automatic switch to backup [OK]

Hint: Automatic failover means automatic switch on failure [OK]

Common Mistakes:

• Thinking failover requires manual intervention
• Confusing failover with backup speed improvements
• Assuming failover backs up data externally

2. Which of the following is the correct way to initiate a replica set in MongoDB shell for automatic failover?

easy

A. db.startReplica()

B. rs.initiate()

C. replicaSet.start()

D. mongo.startReplicaSet()

Solution

1. Step 1: Recall MongoDB replica set initiation command

   The correct command to start a replica set in MongoDB shell is rs.initiate().

2. Step 2: Verify other options are invalid

   Commands like db.startReplica(), replicaSet.start(), and mongo.startReplicaSet() do not exist in MongoDB shell.

3. Final Answer:

   rs.initiate() -> Option B

4. Quick Check:

   Replica set start = rs.initiate() [OK]

Hint: Replica sets start with rs.initiate() command [OK]

Common Mistakes:

• Using non-existent commands to start replica sets
• Confusing database commands with shell commands
• Assuming replica sets start automatically without command

3. Given a MongoDB replica set with three members: Primary, Secondary1, and Secondary2. If the Primary goes down, what will happen automatically?

medium

A. Secondary1 and Secondary2 will both become Primary simultaneously

B. The database will stop accepting writes until manual restart

C. Secondary1 or Secondary2 will be elected as the new Primary

D. The replica set will shut down completely

Solution

1. Step 1: Understand replica set election process

   When the Primary fails, MongoDB automatically elects one Secondary as the new Primary.

2. Step 2: Analyze options for failover behavior

   Only one Secondary becomes Primary; the database continues accepting writes. The other options describe incorrect or impossible behaviors.

3. Final Answer:

   Secondary1 or Secondary2 will be elected as the new Primary -> Option C

4. Quick Check:

   Failover elects one Secondary as Primary [OK]

Hint: Failover elects one Secondary as new Primary [OK]

Common Mistakes:

• Thinking multiple Primaries can exist simultaneously
• Assuming manual restart is needed after Primary failure
• Believing the replica set shuts down on failure

4. You configured a MongoDB replica set but automatic failover is not happening when the primary goes down. What is a likely cause?

medium

A. The replica set has only one member

B. The primary server has too much RAM

C. The secondary servers are running on different OS

D. The replica set was initiated with rs.initiate()

Solution

1. Step 1: Check replica set member count requirement

   Automatic failover requires at least one secondary member to elect a new primary.

2. Step 2: Analyze given options

   If there is only one member, no election can happen, so failover won't work. Other options do not prevent failover.

3. Final Answer:

   The replica set has only one member -> Option A

4. Quick Check:

   Failover needs multiple members [OK]

Hint: Failover needs multiple members, not just one [OK]

Common Mistakes:

• Ignoring the need for multiple replica set members
• Blaming hardware specs for failover issues
• Assuming OS differences block failover

5. In a MongoDB replica set with 5 members, including 3 voting members and 2 non-voting members, what is the minimum number of voting members that must be available to trigger automatic failover?

hard

A. 2 voting members

B. 3 voting members

C. 1 voting member

D. 4 voting members

Solution

1. Step 1: Understand voting majority in replica sets

   Automatic failover requires a majority of voting members to elect a new primary.

2. Step 2: Calculate majority of 3 voting members

   Majority means more than half, so for 3 voting members, majority is 2.

3. Final Answer:

   2 voting members -> Option A

4. Quick Check:

   Majority of 3 voters = 2 [OK]

Hint: Majority of voting members needed for failover [OK]

Common Mistakes:

• Confusing total members with voting members
• Thinking all members must be available
• Miscounting majority as all or one