Why Sentinel provides high availability in Redis - Quick Recap

Recall & Review

beginner

What is Redis Sentinel?

Redis Sentinel is a system that helps keep Redis running smoothly by monitoring Redis servers and automatically fixing problems to avoid downtime.

beginner

How does Sentinel detect failures in Redis?

Sentinel regularly checks Redis servers by sending pings. If a server does not respond after several tries, Sentinel marks it as down.

intermediate

What happens when Sentinel detects a master Redis server failure?

Sentinel promotes one of the slave servers to become the new master, so the system keeps working without manual intervention.

beginner

Why is automatic failover important for high availability?

Automatic failover means the system fixes itself quickly without waiting for a person, reducing downtime and keeping services available.

intermediate

How does Sentinel keep clients informed about the current master?

Sentinel notifies clients about the new master after failover, so clients can connect to the right server without interruption.

What is the main role of Redis Sentinel?

A Monitor Redis servers and handle failover automatically

B Store data permanently

C Backup Redis data to cloud

D Encrypt Redis data

Redis Sentinel monitors Redis servers and automatically manages failover to keep the system available.

How does Sentinel know a Redis master is down?

A It checks the disk space

B It receives an error report from clients

C It stops receiving pings from the master

D It waits for manual confirmation

Sentinel sends regular pings to the master and marks it down if it stops responding.

What does Sentinel do after detecting a master failure?

A Promotes a slave to master

B Deletes all data

C Shuts down all Redis servers

D Sends an email alert only

Sentinel promotes a slave to master to keep Redis available without manual steps.

Why is client notification important in Sentinel?

A To reset client passwords

B To send marketing messages

C To log client IP addresses

D To update clients about the new master server

Clients need to know the current master to connect correctly after failover.

Which feature of Sentinel helps reduce downtime?

A Manual restart

B Automatic failover

C Data compression

D User authentication

Automatic failover lets Sentinel quickly fix failures without waiting for human action.

Explain how Redis Sentinel provides high availability in simple terms.

Think about how Sentinel watches servers and fixes problems without waiting for a person.

Describe the failover process managed by Redis Sentinel.

Focus on the steps Sentinel takes from noticing a problem to fixing it.

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