Cluster failover in Redis - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is cluster failover in Redis?

Cluster failover in Redis is the process where a replica node automatically takes over as the master if the current master node fails, ensuring continuous availability.

beginner

What role does a replica play during a Redis cluster failover?

During failover, a replica is promoted to master to replace the failed master, allowing the cluster to keep serving requests without interruption.

intermediate

How does Redis detect a master failure in a cluster?

Redis uses a consensus of nodes called a quorum to detect if a master is unreachable or down, triggering failover if confirmed.

intermediate

What is the difference between manual and automatic failover in Redis clusters?

Manual failover requires an administrator to promote a replica, while automatic failover happens automatically when the cluster detects a master failure.

beginner

Why is failover important in a Redis cluster?

Failover ensures high availability by minimizing downtime and data loss when a master node fails, keeping the cluster operational.

What happens during a Redis cluster failover?

A All data is deleted

B The cluster shuts down

C A replica is promoted to master

D The master node restarts automatically

During failover, a replica node is promoted to master to replace the failed master.

How does Redis decide to start a failover?

A When a quorum of nodes agree the master is down

B When a user manually restarts the cluster

C When the master node sends a restart signal

D When the replica nodes are empty

Redis uses a quorum of nodes to detect master failure and trigger failover.

Which node becomes master after failover?

A The old master node

B A replica node

C A random node

D The cluster manager

A replica node is promoted to master during failover.

What is NOT a benefit of Redis cluster failover?

A Permanent data deletion

B Automatic recovery

C High availability

D Data loss prevention

Failover prevents downtime and data loss; it does not cause permanent data deletion.

Manual failover in Redis requires:

A No human intervention

B Automatic detection of failure

C A quorum of nodes

D An administrator to promote a replica

Manual failover requires an administrator to promote a replica to master.

Explain how Redis cluster failover works and why it is important.

Think about what happens when the master node stops working and how the cluster keeps running.

Describe the difference between manual and automatic failover in Redis clusters.

Consider who or what triggers the failover.

Practice

1. What is the main purpose of cluster failover in Redis?

easy

A. To backup data to an external storage

B. To clear all keys from the database

C. To increase the number of replicas manually

D. To switch a replica to master if the current master fails

Solution

1. Step 1: Understand cluster failover concept

   Cluster failover automatically promotes a replica to master when the current master fails.

2. Step 2: Identify the main purpose

   This process ensures Redis availability without manual intervention.

3. Final Answer:

   To switch a replica to master if the current master fails -> Option D

4. Quick Check:

   Failover = switch replica to master [OK]

Hint: Failover means replica becomes master on failure [OK]

Common Mistakes:

• Confusing failover with backup
• Thinking failover increases replicas
• Assuming failover clears data

2. Which Redis command syntax correctly triggers a manual failover on a replica node?

easy

A. CLUSTER FAILOVER

B. FAILOVER CLUSTER

C. CLUSTER FAILOVER NOW

D. FAILOVER REPLICA

Solution

1. Step 1: Recall Redis failover command syntax

   The correct command to trigger failover is CLUSTER FAILOVER.

2. Step 2: Check options for syntax correctness

   Options B, C, and D are invalid Redis commands or incorrect order.

3. Final Answer:

   CLUSTER FAILOVER -> Option A

4. Quick Check:

   Correct command = CLUSTER FAILOVER [OK]

Hint: Remember command starts with CLUSTER then FAILOVER [OK]

Common Mistakes:

• Swapping command words order
• Adding invalid keywords
• Using non-existent commands

3. Given a Redis cluster where the master node fails, what will happen if you run CLUSTER FAILOVER FORCE on a replica?

medium

A. The replica deletes all its data before failing over

B. The replica waits for the master to recover before failing over

C. The replica immediately becomes master regardless of cluster state

D. The command returns an error because FORCE is invalid

Solution

1. Step 1: Understand FORCE option in failover

   FORCE forces the replica to become master immediately, ignoring cluster state.

2. Step 2: Analyze other options

   Waiting for master recovery is default without FORCE; FORCE does not cause errors or data deletion.

3. Final Answer:

   The replica immediately becomes master regardless of cluster state -> Option C

4. Quick Check:

   FORCE = immediate failover [OK]

Hint: FORCE triggers instant failover ignoring cluster state [OK]

Common Mistakes:

• Thinking FORCE waits for master
• Assuming FORCE causes errors
• Believing FORCE deletes data

4. You tried running CLUSTER FAILOVER TAKEOVER on a replica but got an error. What is the most likely cause?

medium

A. The TAKEOVER option is not supported in Redis

B. The replica is not connected to the cluster

C. The replica is already the master

D. The command syntax is incorrect

Solution

1. Step 1: Understand TAKEOVER option requirements

   TAKEOVER forces failover even if the master is alive but requires cluster connectivity.

2. Step 2: Identify error cause

   If the replica is disconnected, the command fails with an error.

3. Final Answer:

   The replica is not connected to the cluster -> Option B

4. Quick Check:

   Disconnected replica causes TAKEOVER error [OK]

Hint: Replica must be connected for TAKEOVER to work [OK]

Common Mistakes:

• Assuming TAKEOVER is unsupported
• Ignoring replica connection status
• Thinking syntax is wrong

5. In a Redis cluster with multiple replicas, which failover option should you use to safely promote a replica without risking data loss, and why?

hard

A. Use CLUSTER FAILOVER without options to allow safe automatic failover

B. Use CLUSTER FAILOVER FORCE to force immediate promotion regardless of state

C. Use CLUSTER FAILOVER TAKEOVER to take over even if master is alive

D. Manually disconnect the master before failover

Solution

1. Step 1: Review failover options and safety

   Default CLUSTER FAILOVER waits for safe conditions, avoiding data loss.

2. Step 2: Compare with FORCE and TAKEOVER risks

   FORCE and TAKEOVER can cause data loss by ignoring cluster state or master status.

3. Step 3: Consider manual disconnection risks

   Manually disconnecting master is risky and not recommended for safe failover.

4. Final Answer:

   Use CLUSTER FAILOVER without options to allow safe automatic failover -> Option A

5. Quick Check:

   Safe failover = default CLUSTER FAILOVER [OK]

Hint: Default failover is safest to avoid data loss [OK]

Common Mistakes:

• Using FORCE or TAKEOVER without understanding risks
• Manually disconnecting master unnecessarily
• Assuming all failover options are equally safe