Cluster failover in Redis - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What happens during a Redis cluster failover?

In a Redis cluster, when a master node fails, what is the expected behavior during failover?

A A slave node is promoted to master to continue serving requests.

B The cluster shuts down all nodes to prevent data loss.

C Clients automatically reconnect to the failed master node.

D The cluster deletes all data on the failed master node.

💡 Hint

Think about how Redis maintains availability when a master fails.

During failover, Redis promotes a slave node to master to keep the cluster available without data loss.

❓ query_result

intermediate

Identify the output of the failover status command

What is the output of the Redis CLI command `CLUSTER FAILOVER` when executed on a slave node during failover?

Redis

CLUSTER FAILOVER

A "PENDING"

B "FAIL"

C An error: ERR This node is not a slave

D "OK"

💡 Hint

The command is used to trigger manual failover from a slave.

The command returns "OK" when the slave node successfully starts the failover process.

📝 Syntax

advanced

Which command syntax triggers a manual failover with force?

Select the correct Redis command syntax to force a manual failover on a slave node.

A CLUSTER FAILOVER IMMEDIATE

B CLUSTER FAILOVER TAKEOVER

C CLUSTER FAILOVER NOW

D CLUSTER FAILOVER START

💡 Hint

The TAKEOVER option bypasses some checks during failover.

The correct syntax to force failover is `CLUSTER FAILOVER TAKEOVER`.

❓ optimization

advanced

Optimizing failover detection time in Redis cluster

Which configuration change will reduce the time Redis cluster takes to detect a master node failure and start failover?

A Decrease `cluster-node-timeout` value.

B Increase `cluster-slave-no-failover` setting.

C Disable `cluster-require-full-coverage`.

D Increase `cluster-replica-validity-factor` value.

💡 Hint

Failover detection depends on how quickly nodes consider others unreachable.

Lowering `cluster-node-timeout` makes nodes detect failures faster, triggering quicker failover.

🔧 Debug

expert

Why does manual failover fail with ERR when forced on a master node?

You run `CLUSTER FAILOVER TAKEOVER` on a Redis node that is currently a master. The command returns an error: `ERR This node is not a slave`. Why does this happen?

A The cluster is not enabled on this node.

B The node is in read-only mode and cannot failover.

C Failover can only be forced on slave nodes, not masters.

D The node has no connected clients.

💡 Hint

Failover means promoting a slave to master, so the command must run on a slave.

Only slave nodes can initiate failover to become master; forcing failover on a master causes this error.

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