Automatic failover in Redis - Mini Project: Build & Apply

Automatic Failover Setup in Redis

📖 Scenario: You are managing a Redis database for a small online store. To ensure the store stays online even if the main Redis server fails, you want to set up automatic failover using Redis Sentinel.

🎯 Goal: Set up a Redis Sentinel configuration that monitors a Redis master server and automatically promotes a replica to master if the master fails.

📋 What You'll Learn

Create a Redis master configuration with a specific name.

Create at least two Redis replica configurations.

Configure Redis Sentinel to monitor the master with a quorum of 2.

Set the failover timeout to 10000 milliseconds.

💡 Why This Matters

🌍 Real World

Automatic failover ensures that if the main Redis server crashes, a replica takes over immediately, keeping applications running smoothly without manual intervention.

💼 Career

Understanding Redis Sentinel and failover is important for roles like DevOps engineers, backend developers, and system administrators who maintain reliable and scalable database systems.

1

Create Redis master configuration

Create a Redis master configuration file named redis-master.conf with the following settings: set port 6379 and daemonize yes.

Redis

# Create redis-master.conf with port 6379 and daemonize yes
# Your code here

Hint

Use port 6379 to set the port and daemonize yes to run Redis in the background.

2

Create Redis replica configurations

Create two Redis replica configuration files named redis-replica1.conf and redis-replica2.conf. Each should have port 6380 and port 6381 respectively, daemonize yes, and set replicaof 127.0.0.1 6379 to replicate the master.

Redis

port 6379
daemonize yes
# Create redis-replica1.conf with port 6380, daemonize yes, and replicaof 127.0.0.1 6379
# Your code here

Hint

Each replica must have its own port and replicate the master at 127.0.0.1 port 6379.

3

Configure Redis Sentinel to monitor the master

Create a Redis Sentinel configuration file named sentinel.conf. Add the line sentinel monitor mymaster 127.0.0.1 6379 2 to monitor the master named mymaster at IP 127.0.0.1 port 6379 with a quorum of 2. Also add sentinel down-after-milliseconds mymaster 5000 and sentinel failover-timeout mymaster 10000.

Redis

# redis-master.conf
port 6379
daemonize yes

# redis-replica1.conf
port 6380
daemonize yes
replicaof 127.0.0.1 6379

# redis-replica2.conf
port 6381
daemonize yes
replicaof 127.0.0.1 6379

# Create sentinel.conf with monitor and failover settings
# Your code here

Hint

The sentinel monitor line tells Sentinel what master to watch and the quorum needed. The other lines set timing for failover.

4

Complete Sentinel configuration with notification script

In sentinel.conf, add the line sentinel notification-script mymaster /usr/local/bin/notify.sh to specify a notification script that runs on failover events.

Redis

# redis-master.conf
port 6379
daemonize yes

# redis-replica1.conf
port 6380
daemonize yes
replicaof 127.0.0.1 6379

# redis-replica2.conf
port 6381
daemonize yes
replicaof 127.0.0.1 6379

# sentinel.conf
sentinel monitor mymaster 127.0.0.1 6379 2
sentinel down-after-milliseconds mymaster 5000
sentinel failover-timeout mymaster 10000
# Add notification script line below
# Your code here

Hint

This line tells Sentinel to run a script when failover events happen, useful for alerts.

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