Automatic failover in Redis - Time & Space Complexity

Time Complexity: Automatic failover

O(n)

Understanding Time Complexity

When Redis automatically switches to a backup server after a failure, it needs to check the status of servers and decide quickly.

We want to understand how the time it takes to do this changes as the number of servers grows.

Scenario Under Consideration

Analyze the time complexity of the following Redis Sentinel automatic failover process.

SENTINEL masters
SENTINEL slaves <master-name>
SENTINEL is-master-down-by-addr <ip> <port> <current-epoch>
SENTINEL failover <master-name>
    

This sequence checks master and slave servers, detects if the master is down, and triggers failover to a slave.

Identify Repeating Operations

In this process, the main repeating operations are:

• Primary operation: Checking the status of each slave server for the master.
• How many times: Once for each slave connected to the master.

How Execution Grows With Input

As the number of slaves increases, the time to check their status grows roughly in a straight line.

Input Size (number of slaves)	Approx. Operations
10	10 status checks
100	100 status checks
1000	1000 status checks

Pattern observation: The work grows directly with the number of slaves to check.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete failover checks grows in a straight line as the number of slave servers increases.

Common Mistake

[X] Wrong: "Failover time stays the same no matter how many slaves there are."

[OK] Correct: Because Redis must check each slave's status, more slaves mean more checks and more time.

Interview Connect

Understanding how failover time grows helps you explain system reliability and scaling in real projects.

Self-Check

"What if Redis used a way to check all slaves at once instead of one by one? How would the time complexity change?"

Practice

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

easy

A. To backup data to an external storage

B. To increase the speed of Redis queries

C. To switch to a backup server if the main server fails

D. To encrypt data during transmission

Solution

1. Step 1: Understand the concept of failover

   Failover means switching to a backup system when the main one stops working.

2. Step 2: Apply this to Redis context

   Redis automatic failover switches to a backup Redis server if the main one fails.

3. Final Answer:

   To switch to a backup server if the main server fails -> Option C

4. Quick Check:

   Automatic failover = switch to backup server [OK]

Hint: Failover means backup server takes over on failure [OK]

Common Mistakes:

• Confusing failover with data backup
• Thinking failover speeds up queries
• Mixing failover with encryption

2. Which Redis component is responsible for managing automatic failover?

easy

A. Redis Cluster

B. Redis Sentinel

C. Redis Streams

D. Redis Modules

Solution

1. Step 1: Identify Redis components related to failover

   Redis Sentinel is designed to monitor Redis servers and manage failover.

2. Step 2: Confirm other options are unrelated

   Redis Cluster manages sharding, Streams handle data streams, Modules add features but don't manage failover.

3. Final Answer:

   Redis Sentinel -> Option B

4. Quick Check:

   Failover manager = Sentinel [OK]

Hint: Sentinel monitors and triggers failover in Redis [OK]

Common Mistakes:

• Confusing Sentinel with Cluster
• Thinking Streams handle failover
• Assuming Modules manage failover

3. Given a Redis setup with 3 Sentinel instances monitoring 1 master and 2 replicas, what happens if the master fails?

medium

A. Sentinels promote one replica to master automatically

B. All Sentinels shut down to prevent split-brain

C. Clients lose connection permanently

D. The master restarts automatically without promotion

Solution

1. Step 1: Understand Sentinel quorum and failover

   With multiple Sentinels, they agree on master failure and promote a replica.

2. Step 2: Analyze options

   Sentinels do not shut down; clients reconnect after failover; master does not restart automatically.

3. Final Answer:

   Sentinels promote one replica to master automatically -> Option A

4. Quick Check:

   Master failure triggers replica promotion [OK]

Hint: Sentinels elect new master when original fails [OK]

Common Mistakes:

• Thinking Sentinels shut down on failure
• Assuming clients lose connection forever
• Believing master restarts without failover

4. You configured Redis Sentinel with only one instance monitoring a master and replicas. What is a likely problem with automatic failover?

medium

A. Failover may not happen due to lack of quorum

B. Sentinel will promote multiple replicas simultaneously

C. Sentinel will delete all data on replicas

D. Failover will happen instantly without checks

Solution

1. Step 1: Understand Sentinel quorum requirement

   Sentinel needs multiple instances to agree (quorum) before failover.

2. Step 2: Analyze single Sentinel behavior

   With only one Sentinel, no quorum exists, so failover may not trigger reliably.

3. Final Answer:

   Failover may not happen due to lack of quorum -> Option A

4. Quick Check:

   Single Sentinel lacks quorum for failover [OK]

Hint: Multiple Sentinels needed for reliable failover [OK]

Common Mistakes:

• Thinking one Sentinel can safely failover
• Believing Sentinel deletes replica data
• Assuming failover is instant without checks

5. In a Redis master-replica setup with automatic failover, which combination ensures the highest availability?

hard

A. One master, no replicas, one Sentinel instance

B. One master, one replica, one Sentinel instance

C. Multiple masters, no replicas, multiple Sentinel instances

D. One master, multiple replicas, multiple Sentinel instances

Solution

1. Step 1: Identify components for high availability

   Multiple replicas provide backup data; multiple Sentinels provide reliable failover decisions.

2. Step 2: Evaluate each option

   One master, one replica, one Sentinel instance lacks multiple Sentinels; C has multiple masters causing conflicts; D lacks replicas and multiple Sentinels.

3. Final Answer:

   One master, multiple replicas, multiple Sentinel instances -> Option D

4. Quick Check:

   Replicas + multiple Sentinels = high availability [OK]

Hint: Use multiple replicas and Sentinels for best failover [OK]

Common Mistakes:

• Thinking one Sentinel is enough
• Confusing multiple masters with high availability
• Ignoring replicas in failover setup