Automatic failover in Redis

Introduction

Automatic failover helps keep your Redis database working even if one server stops. It switches to a backup server without you doing anything.

You want your Redis service to stay online during server problems.

You have multiple Redis servers and want one to take over if the main one fails.

You want to avoid manual fixes when a Redis server crashes.

You run a website or app that needs fast data access all the time.

You want to improve reliability without extra work.

Syntax

Redis

Use Redis Sentinel configuration files and commands to set up automatic failover.

Basic Sentinel command example:
SENTINEL MONITOR <master-name> <ip> <port> <quorum>

Where:
- <master-name> is a name you choose for your master server
- <ip> and <port> point to the master server
- <quorum> is the number of Sentinels that must agree a failover is needed

Redis Sentinel is the tool that manages automatic failover.

You need at least 3 Sentinel instances for reliable failover decisions.

Examples

This tells Sentinel to watch a master Redis server named 'mymaster' at IP 127.0.0.1 and port 6379. It requires 2 Sentinels to agree before failover.

Redis

SENTINEL MONITOR mymaster 127.0.0.1 6379 2

This command forces Sentinel to start a failover for the master named 'mymaster'.

Redis

SENTINEL FAILOVER mymaster

Sample Program

This example shows how Redis Sentinel watches a master and its replica. When the master stops, Sentinel promotes the replica to master automatically.

Redis

# Start Sentinel with config file that includes:
# sentinel monitor mymaster 127.0.0.1 6379 2
# Then simulate master failure and observe automatic failover

# This is a conceptual example, actual commands run in terminal

# Step 1: Start Redis master on port 6379
redis-server --port 6379

# Step 2: Start Redis replica on port 6380
redis-server --port 6380 --replicaof 127.0.0.1 6379

# Step 3: Start Sentinel with config sentinel.conf
redis-sentinel sentinel.conf

# Step 4: Stop master to trigger failover
redis-cli -p 6379 SHUTDOWN

# Step 5: Sentinel promotes replica to master automatically

# Step 6: Check new master
redis-cli -p 6380 INFO replication

Important Notes

Automatic failover requires careful setup of Sentinel and Redis replicas.

Failover can cause a short pause while the new master is chosen.

Test failover in a safe environment before using in production.

Summary

Automatic failover keeps Redis running by switching to a backup server if the main one fails.

Redis Sentinel manages failover by monitoring servers and deciding when to switch.

You need multiple Sentinel instances and replicas for reliable failover.

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