Monitoring with Sentinel in Redis - Mini Project: Build & Apply

Monitoring with Sentinel

📖 Scenario: You are managing a Redis database that needs to be highly available. To do this, you will set up Redis Sentinel to monitor the Redis master and its replicas. Sentinel will help detect failures and promote a replica to master if needed.

🎯 Goal: Set up a basic Redis Sentinel configuration to monitor a Redis master instance. You will create the initial Sentinel configuration, add monitoring settings, and then check the Sentinel output to confirm it is monitoring the master.

📋 What You'll Learn

Create a Redis Sentinel configuration file named sentinel.conf.

Add a monitoring configuration for a Redis master named mymaster with IP 127.0.0.1 and port 6379.

Set the quorum to 2 in the Sentinel configuration.

Start Redis Sentinel with the configuration file and verify it is monitoring the master.

💡 Why This Matters

🌍 Real World

Redis Sentinel is used in production to keep Redis databases highly available by monitoring and automatically handling failures.

💼 Career

Understanding Sentinel setup is important for DevOps roles managing Redis clusters to ensure service reliability and uptime.

1

Create the initial Sentinel configuration file

Create a file named sentinel.conf and add the line port 26379 to set the Sentinel port.

Redis

# Create sentinel.conf file and add port configuration
# Your code here

Hint

The Sentinel listens on port 26379 by default. You need to specify this in the configuration file.

2

Add monitoring configuration for the Redis master

In 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 and port 6379 with quorum 2.

Redis

port 26379
# Add sentinel monitor configuration below
# Your code here

Hint

The sentinel monitor command tells Sentinel which master to watch and the quorum needed to agree on failover.

3

Start Redis Sentinel with the configuration

Run the command redis-sentinel sentinel.conf in your terminal to start Redis Sentinel with the configuration file.

Redis

port 26379
sentinel monitor mymaster 127.0.0.1 6379 2
# Start Redis Sentinel with the config file
# Your code here

Hint

Use the redis-sentinel command followed by the config file name to start Sentinel.

4

Check Sentinel is monitoring the master

Run redis-cli -p 26379 SENTINEL masters to display the monitored masters and confirm mymaster is listed.

Redis

port 26379
sentinel monitor mymaster 127.0.0.1 6379 2
# Command to start Redis Sentinel:
redis-sentinel sentinel.conf
# Run command to check monitored masters
# Your code here

Hint

The output should include a line with name:mymaster showing the master is monitored.

Practice

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

easy

A. To provide a graphical user interface for Redis

B. To automatically detect Redis server failures and promote replicas

C. To increase Redis memory capacity

D. To store data persistently on disk

Solution

1. Step 1: Understand Sentinel's role

   Sentinel monitors Redis servers to detect failures automatically.

2. Step 2: Identify Sentinel's key feature

   It can promote replicas to master to keep Redis available during failures.

3. Final Answer:

   To automatically detect Redis server failures and promote replicas -> Option B

4. Quick Check:

   Sentinel monitors and promotes replicas [OK]

Hint: Sentinel watches and promotes Redis servers automatically [OK]

Common Mistakes:

• Confusing Sentinel with data storage
• Thinking Sentinel increases memory
• Assuming Sentinel provides GUI

2. Which command correctly tells Sentinel to monitor a Redis master named mymaster at IP 192.168.1.10 on port 6379 with quorum 2?

easy

A. sentinel monitor mymaster 192.168.1.10 6379

B. sentinel watch mymaster 192.168.1.10 6379 2

C. sentinel add mymaster 192.168.1.10 6379 2

D. sentinel monitor mymaster 192.168.1.10 6379 2

Solution

1. Step 1: Recall Sentinel monitor syntax

   The correct syntax is: sentinel monitor <name> <ip> <port> <quorum>.

2. Step 2: Match the command to syntax

   sentinel monitor mymaster 192.168.1.10 6379 2 matches the syntax exactly with all required parameters.

3. Final Answer:

   sentinel monitor mymaster 192.168.1.10 6379 2 -> Option D

4. Quick Check:

   Correct sentinel monitor syntax [OK]

Hint: Use 'sentinel monitor' with name, IP, port, quorum [OK]

Common Mistakes:

• Using 'sentinel watch' instead of 'monitor'
• Omitting quorum number
• Using 'sentinel add' which is invalid

3. Given the following Sentinel configuration snippet:

sentinel monitor mymaster 10.0.0.5 6379 2
sentinel down-after-milliseconds mymaster 5000
sentinel failover-timeout mymaster 10000

What does the down-after-milliseconds setting control?

medium

A. Time Redis waits before shutting down

B. Time replicas wait before syncing

C. Time Sentinel waits before marking master as down

D. Time Sentinel waits before starting failover

Solution

1. Step 1: Understand 'down-after-milliseconds'

   This setting defines how long Sentinel waits to consider the master as unreachable.

2. Step 2: Match setting to behavior

   It controls the time Sentinel waits before marking the master as down.

3. Final Answer:

   Time Sentinel waits before marking master as down -> Option C

4. Quick Check:

   down-after-milliseconds = time to mark down [OK]

Hint: down-after-milliseconds sets master down detection time [OK]

Common Mistakes:

• Confusing with Redis shutdown time
• Thinking it controls replica sync delay
• Assuming it delays failover start

4. You configured Sentinel with:

sentinel monitor mymaster 10.0.0.5 6379 2

But Sentinel never triggers failover even when the master is down. What is a likely cause?

medium

A. Quorum is set too high for available Sentinels

B. Master IP address is incorrect

C. Sentinel service is not running

D. Redis master port is blocked by firewall

Solution

1. Step 1: Understand quorum role

   Quorum is the number of Sentinels that must agree master is down to trigger failover.

2. Step 2: Analyze failover condition

   If quorum is higher than available Sentinels, failover never triggers.

3. Final Answer:

   Quorum is set too high for available Sentinels -> Option A

4. Quick Check:

   Failover needs quorum Sentinels agreeing [OK]

Hint: Check quorum matches number of running Sentinels [OK]

Common Mistakes:

• Ignoring quorum size
• Assuming IP or port issues cause failover block
• Not verifying Sentinel service status

5. You have 3 Sentinel instances monitoring a Redis master with quorum 2. One Sentinel detects the master is down and starts failover, but the other two Sentinels disagree. What will happen?

hard

A. Failover will not proceed until at least 2 Sentinels agree

B. Failover proceeds immediately with one Sentinel's decision

C. Sentinel with disagreement will restart Redis master

D. All Sentinels shut down to avoid split-brain

Solution

1. Step 1: Understand quorum in failover

   Failover requires quorum number of Sentinels to agree master is down.

2. Step 2: Analyze scenario with 3 Sentinels and quorum 2

   Only one Sentinel detects down, so quorum not reached; failover waits.

3. Final Answer:

   Failover will not proceed until at least 2 Sentinels agree -> Option A

4. Quick Check:

   Failover needs quorum agreement [OK]

Hint: Failover needs quorum agreement, not just one Sentinel [OK]

Common Mistakes:

• Thinking one Sentinel can trigger failover alone
• Assuming Sentinels restart Redis master
• Believing Sentinels shut down on disagreement