Sentinel architecture in Redis - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Role of Sentinel in Redis architecture

What is the primary role of Redis Sentinel in a Redis deployment?

A To act as a caching layer between clients and Redis

B To monitor Redis instances and perform automatic failover if the master fails

C To provide a graphical user interface for Redis management

D To store data persistently on disk for Redis

💡 Hint

Think about what happens when the master Redis server stops working.

Redis Sentinel monitors Redis servers and automatically promotes a slave to master if the current master fails, ensuring high availability.

❓ query_result

intermediate

Sentinel command output interpretation

Given the Redis Sentinel command SENTINEL masters, what kind of information does it return?

A A list of all monitored master nodes with their status and configuration

B The memory usage statistics of the Redis server

C The list of connected clients to the Redis server

D The current keys stored in the Redis database

💡 Hint

Sentinel monitors masters, so the command should show details about them.

The SENTINEL masters command returns details about all master nodes Sentinel is monitoring, including their health and configuration.

📝 Syntax

advanced

Correct Sentinel configuration snippet

Which of the following Redis Sentinel configuration snippets correctly defines a master named mymaster running on IP 192.168.1.100 and port 6379 with quorum 2?

A sentinel mymaster monitor 192.168.1.100 6379 2

B monitor sentinel mymaster 192.168.1.100 6379 2

C sentinel monitor mymaster 192.168.1.100 6379 2

D monitor mymaster sentinel 192.168.1.100 6379 2

💡 Hint

The correct syntax starts with the word 'sentinel' followed by 'monitor'.

The correct syntax for monitoring a master in Sentinel config is: sentinel monitor <master-name> <ip> <port> <quorum>.

❓ optimization

advanced

Optimizing Sentinel quorum for failover

In a Redis Sentinel setup with 5 Sentinel nodes, what is the recommended quorum value to ensure reliable failover without risking split-brain?

A 2

B 1

C 5

D 3

💡 Hint

Quorum should be a majority of Sentinels to avoid split-brain.

With 5 Sentinels, quorum should be at least 3 to ensure a majority agrees on failover, preventing split-brain scenarios.

🔧 Debug

expert

Diagnosing Sentinel failover failure

A Redis Sentinel cluster is not performing failover when the master goes down. Which of the following is the most likely cause?

A The quorum value is set higher than the number of available Sentinel nodes

B The Redis slaves are configured with different passwords

C The Redis master has persistence enabled

D The Redis clients are using pipelining

💡 Hint

Failover requires enough Sentinels to agree; if quorum is too high, failover won't trigger.

If quorum is set higher than the number of Sentinels running, failover cannot be agreed upon and will not happen.

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