Automatic failover in Redis - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is automatic failover in Redis?

Automatic failover is a process where Redis automatically switches to a replica if the master node fails, ensuring the system keeps working without manual intervention.

beginner

Which Redis feature helps manage automatic failover?

Redis Sentinel is the feature that monitors Redis masters and replicas, and triggers automatic failover when a master fails.

intermediate

What role does a Sentinel play in Redis automatic failover?

A Sentinel watches the master and replicas, detects failures, and coordinates the promotion of a replica to master during failover.

beginner

Why is automatic failover important in Redis?

It keeps Redis available and responsive by quickly recovering from master failures without manual steps, reducing downtime.

intermediate

What happens to clients during Redis automatic failover?

Clients may experience a short delay while the failover happens, but then they reconnect to the new master automatically if configured properly.

What triggers Redis automatic failover?

A Manual restart of Redis server

B Master node failure detected by Sentinel

C Client disconnection

D Replica synchronization

Redis Sentinel detects when the master node fails and triggers automatic failover to a replica.

Which Redis component is responsible for monitoring and failover?

A Redis Cluster

B Redis Module

C Redis Client

D Redis Sentinel

Redis Sentinel monitors Redis nodes and manages automatic failover.

During automatic failover, what happens to the replica?

A It becomes the new master

B It shuts down

C It disconnects clients

D It deletes data

The replica is promoted to master to continue serving requests.

What is a key benefit of automatic failover in Redis?

A Data is lost during failover

B Manual intervention is required

C Downtime is minimized

D Clients must reconnect manually

Automatic failover minimizes downtime by quickly switching to a replica.

What must clients do to handle failover smoothly?

A Use Sentinel-aware clients that can discover the new master

B Restart manually after failover

C Ignore failover events

D Disconnect permanently

Clients that support Sentinel can automatically find the new master after failover.

Explain how Redis automatic failover works and the role of Sentinel.

Think about how Redis keeps working when the main server stops.

Describe the benefits of using automatic failover in a Redis setup.

Why is it good to have failover happen automatically?

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