Sentinel architecture in Redis - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Redis Sentinel?

Redis Sentinel is a system that helps monitor Redis servers, automatically switch to a backup if the main server fails, and notify users about the system status.

beginner

What are the main roles of Redis Sentinel?

Redis Sentinel has three main roles: monitoring Redis servers, notifying clients about changes, and performing automatic failover to a backup server if the main one stops working.

intermediate

How does Redis Sentinel decide to failover to a backup server?

Sentinel checks if the main Redis server is down by asking other Sentinels and clients. If enough agree the server is unreachable, Sentinel promotes a backup to be the new main server.

intermediate

What is a quorum in Redis Sentinel?

A quorum is the minimum number of Sentinel instances that must agree a Redis server is down before starting a failover. This prevents mistakes from a single Sentinel's wrong judgment.

beginner

Why is it recommended to run multiple Sentinel instances?

Running multiple Sentinel instances improves reliability by allowing them to vote on server status, reducing false failovers and ensuring the system can handle Sentinel failures.

What is the primary purpose of Redis Sentinel?

A To store data persistently

B To monitor Redis servers and manage automatic failover

C To provide a user interface for Redis

D To backup Redis data to cloud storage

Redis Sentinel monitors Redis servers and automatically switches to a backup if the main server fails.

What does Redis Sentinel use to decide if a master server is down?

A Votes from multiple Sentinel instances

B A single Sentinel's opinion

C Client application logs

D Manual user input

Sentinel requires a quorum of Sentinels to agree a server is down before failover.

What happens during a failover in Redis Sentinel?

A Data is deleted

B Clients disconnect permanently

C All servers restart

D A slave is promoted to master

During failover, Sentinel promotes a slave to become the new master.

Why is it important to have multiple Sentinel instances?

A To avoid false failovers and improve reliability

B To increase data storage capacity

C To speed up Redis queries

D To reduce network traffic

Multiple Sentinels vote to confirm failures, preventing mistakes and improving system reliability.

What is the role of notifications in Redis Sentinel?

A To backup data automatically

B To send emails to users

C To inform clients about server status changes

D To encrypt Redis data

Sentinel notifies clients when the master changes or other important events happen.

Explain how Redis Sentinel monitors and manages failover in a Redis setup.

Think about how Sentinel watches servers and what it does when the main server stops working.

Describe why running multiple Sentinel instances is important and how they work together.

Consider how decisions are made and why one Sentinel alone is not enough.

Practice

1. What is the main purpose of Redis Sentinel in a Redis setup?

easy

A. To compress Redis data for faster transmission

B. To store large amounts of data persistently

C. To monitor Redis servers and automatically handle failover

D. To provide a graphical user interface for Redis

Solution

1. Step 1: Understand Sentinel's role

   Redis Sentinel monitors Redis servers to detect failures.

2. Step 2: Identify Sentinel's key feature

   It automatically switches to a backup server if the main one fails, ensuring availability.

3. Final Answer:

   To monitor Redis servers and automatically handle failover -> Option C

4. Quick Check:

   Sentinel = automatic failover [OK]

Hint: Sentinel watches servers and switches on failure [OK]

Common Mistakes:

• Confusing Sentinel with data storage
• Thinking Sentinel provides UI
• Assuming Sentinel compresses data

2. Which of the following is the correct way to start a Redis Sentinel instance using the command line?

easy

A. redis-sentinel /path/to/sentinel.conf

B. redis-server --sentinel /path/to/sentinel.conf

C. redis-cli sentinel start /path/to/sentinel.conf

D. redis-start sentinel /path/to/sentinel.conf

Solution

1. Step 1: Recall Redis Sentinel startup command

   The correct command to start Sentinel is redis-sentinel followed by the config file.

2. Step 2: Check each option

   redis-sentinel /path/to/sentinel.conf matches the correct syntax; others are invalid commands or flags.

3. Final Answer:

   redis-sentinel /path/to/sentinel.conf -> Option A

4. Quick Check:

   Sentinel starts with redis-sentinel command [OK]

Hint: Sentinel uses redis-sentinel command, not redis-server [OK]

Common Mistakes:

• Using redis-server with --sentinel flag
• Trying to start Sentinel via redis-cli
• Using non-existent redis-start command

3. Given a Redis Sentinel setup monitoring a master named mymaster, what will the command redis-cli -p 26379 SENTINEL get-master-addr-by-name mymaster return?

medium

A. The configuration file path of Sentinel

B. The IP and port of the current master server

C. The list of all slaves under the master

D. An error because the command is invalid

Solution

1. Step 1: Understand the command purpose

   The command queries Sentinel on port 26379 for the address of the master named 'mymaster'.

2. Step 2: Identify expected output

   It returns the IP and port of the current master server Sentinel monitors.

3. Final Answer:

   The IP and port of the current master server -> Option B

4. Quick Check:

   get-master-addr-by-name returns master address [OK]

Hint: get-master-addr-by-name returns master IP and port [OK]

Common Mistakes:

• Confusing master address with slave list
• Expecting config file path as output
• Assuming command is invalid

4. You configured Redis Sentinel but it never triggers failover when the master goes down. Which of the following is the most likely cause?

medium

A. Sentinel quorum is not reached due to insufficient Sentinel instances

B. The master server has persistence disabled

C. The Redis version is too new for Sentinel

D. The client application does not use SSL

Solution

1. Step 1: Understand failover conditions

   Sentinel requires a quorum of Sentinel instances to agree before failover.

2. Step 2: Analyze the cause of no failover

   If quorum is not reached, Sentinel will not promote a slave to master.

3. Final Answer:

   Sentinel quorum is not reached due to insufficient Sentinel instances -> Option A

4. Quick Check:

   Failover needs quorum agreement [OK]

Hint: Failover needs quorum; check Sentinel count [OK]

Common Mistakes:

• Blaming persistence for failover
• Assuming Redis version blocks Sentinel
• Thinking SSL affects failover

5. In a Redis Sentinel cluster with 5 Sentinel nodes monitoring 3 Redis masters, how many Sentinel nodes must agree to trigger a failover for a master if the quorum is set to 3?

hard

A. At least 2 Sentinel nodes must agree

B. Only 1 Sentinel node needs to agree

C. All 5 Sentinel nodes must agree

D. At least 3 Sentinel nodes must agree

Solution

1. Step 1: Understand quorum setting

   The quorum setting defines the minimum number of Sentinels that must agree to start failover.

2. Step 2: Apply quorum to the cluster

   With quorum set to 3, at least 3 Sentinel nodes must agree to trigger failover.

3. Final Answer:

   At least 3 Sentinel nodes must agree -> Option D

4. Quick Check:

   Quorum = minimum agreeing Sentinels [OK]

Hint: Quorum number = minimum Sentinels needed for failover [OK]

Common Mistakes:

• Thinking only 1 Sentinel is enough
• Assuming all Sentinels must agree
• Confusing quorum with total Sentinel count