Why Sentinel provides high availability in Redis

Introduction

Sentinel helps keep your Redis database working even if some parts fail. It watches over Redis servers and quickly fixes problems to avoid downtime.

You want your Redis database to keep running even if one server crashes.

You need automatic switching to a backup Redis server without manual work.

You want to be alerted if your Redis servers have problems.

You want to manage multiple Redis servers easily with automatic failover.

Syntax

Redis

Sentinel runs as a separate process and monitors Redis servers.
It uses configuration files to know which servers to watch.
When a master server fails, Sentinel promotes a replica to master automatically.

Sentinel is not a command but a system that runs alongside Redis servers.

It uses a voting system among multiple Sentinel instances to decide on failover.

Examples

This config tells Sentinel to watch a master Redis server at 127.0.0.1:6379 and start failover if it is down for 5 seconds.

Redis

# sentinel.conf example
sentinel monitor mymaster 127.0.0.1 6379 2
sentinel down-after-milliseconds mymaster 5000
sentinel failover-timeout mymaster 60000
sentinel parallel-syncs mymaster 1

This command starts the Sentinel process using the configuration file.

Redis

# Starting Sentinel
redis-sentinel /path/to/sentinel.conf

Sample Program

This example shows how Sentinel works in practice by monitoring and promoting Redis servers automatically.

Redis

# This is a conceptual example, not a query.
# Sentinel monitors Redis master and replicas.
# If master fails, Sentinel promotes a replica automatically.
# Sentinel also notifies clients about the new master.

# To test, stop the master Redis server and watch Sentinel logs.

Important Notes

Sentinel requires at least three Sentinel instances for reliable failover decisions.

Sentinel helps avoid downtime by automatically switching to a healthy Redis server.

Summary

Sentinel watches Redis servers to detect failures quickly.

It automatically promotes a replica to master if the current master fails.

This process keeps your Redis service available without manual intervention.

Practice

1. What is the main reason Redis Sentinel provides high availability?

easy

A. It compresses data to save storage space.

B. It increases the speed of Redis queries.

C. It encrypts Redis data for security.

D. It monitors Redis servers and promotes replicas automatically on failure.

Solution

1. Step 1: Understand Sentinel's role in monitoring

   Sentinel continuously watches Redis servers to detect if the master fails.

2. Step 2: Recognize automatic failover

   When the master fails, Sentinel promotes a replica to master automatically to keep service running.

3. Final Answer:

   It monitors Redis servers and promotes replicas automatically on failure. -> Option D

4. Quick Check:

   Sentinel = Automatic failover [OK]

Hint: Sentinel watches and switches masters automatically [OK]

Common Mistakes:

• Confusing Sentinel with data compression tools
• Thinking Sentinel speeds up queries
• Assuming Sentinel only encrypts data

2. Which of the following is the correct way to configure Redis Sentinel to monitor a master named mymaster on port 6379?

easy

A. sentinel monitor mymaster 127.0.0.1 6379 2

B. sentinel watch mymaster 127.0.0.1 6379 2

C. sentinel track mymaster 127.0.0.1 6379 2

D. sentinel check mymaster 127.0.0.1 6379 2

Solution

1. Step 1: Recall Sentinel configuration command

   The correct command to start monitoring a master is sentinel monitor.

2. Step 2: Verify command syntax

   The syntax is sentinel monitor <name> <ip> <port> <quorum>, matching sentinel monitor mymaster 127.0.0.1 6379 2.

3. Final Answer:

   sentinel monitor mymaster 127.0.0.1 6379 2 -> Option A

4. Quick Check:

   Monitor command = sentinel monitor [OK]

Hint: Use 'sentinel monitor' to watch a master server [OK]

Common Mistakes:

• Using 'watch' instead of 'monitor'
• Confusing 'track' or 'check' commands
• Wrong command syntax order

3. Given a Redis Sentinel setup monitoring a master and two replicas, what will happen if the master server stops responding?

medium

A. Sentinel will promote one replica to master automatically.

B. Sentinel will do nothing and wait for manual restart.

C. Sentinel will shut down all Redis servers.

D. Sentinel will delete all data to prevent corruption.

Solution

1. Step 1: Understand Sentinel's failure detection

   Sentinel detects when the master is down by monitoring its health.

2. Step 2: Recognize Sentinel's failover action

   Upon detecting failure, Sentinel promotes a replica to master automatically to maintain availability.

3. Final Answer:

   Sentinel will promote one replica to master automatically. -> Option A

4. Quick Check:

   Failover = Replica promoted [OK]

Hint: Master down? Sentinel promotes replica automatically [OK]

Common Mistakes:

• Thinking Sentinel waits for manual restart
• Assuming Sentinel shuts down servers
• Believing Sentinel deletes data

4. You configured Redis Sentinel but it never promotes a replica after the master fails. What is the most likely cause?

medium

A. The replicas have more memory than the master.

B. The Redis version is too new for Sentinel to work.

C. Sentinel quorum is not reached due to insufficient Sentinel nodes.

D. Sentinel does not support automatic failover.

Solution

1. Step 1: Understand Sentinel quorum requirement

   Sentinel requires a quorum (minimum number of Sentinels agreeing) to trigger failover.

2. Step 2: Identify cause of no failover

   If quorum is not reached, Sentinel will not promote replicas automatically.

3. Final Answer:

   Sentinel quorum is not reached due to insufficient Sentinel nodes. -> Option C

4. Quick Check:

   Failover needs quorum [OK]

Hint: Check Sentinel quorum count if failover doesn't happen [OK]

Common Mistakes:

• Blaming replica memory size
• Assuming Redis version blocks Sentinel
• Thinking Sentinel lacks failover feature

5. In a Redis Sentinel cluster with 5 Sentinel nodes monitoring 3 replicas and 1 master, what happens if 2 Sentinels lose network connectivity but the master fails?

hard

A. All replicas are shut down to avoid split-brain.

B. Failover proceeds because quorum of Sentinels still agree on master failure.

C. Sentinel automatically adds new nodes to replace disconnected ones.

D. Failover is blocked because any Sentinel failure stops the process.

Solution

1. Step 1: Calculate quorum in a 5-node Sentinel cluster

   Quorum is usually a majority; with 5 nodes, quorum is 3.

2. Step 2: Assess failover with 2 disconnected Sentinels

   3 Sentinels remain connected, so quorum is met and failover proceeds.

3. Step 3: Understand Sentinel behavior on partial network loss

   Sentinel does not block failover if quorum is reached despite some nodes being disconnected.

4. Final Answer:

   Failover proceeds because quorum of Sentinels still agree on master failure. -> Option B

5. Quick Check:

   Quorum met = failover proceeds [OK]

Hint: Failover needs majority Sentinels, not all connected [OK]

Common Mistakes:

• Thinking any Sentinel loss blocks failover
• Assuming Sentinel auto-adds nodes
• Believing replicas shut down on master failure