Multiple Sentinel instances in Redis - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Multiple Sentinel Instances

Why is it recommended to run multiple Redis Sentinel instances monitoring the same master?

A To enable Redis to store more data by distributing it across Sentinels

B To increase the chance of automatic failover by achieving a quorum among Sentinels

C To allow clients to connect to multiple masters simultaneously

D To reduce the memory usage on the Redis master server

💡 Hint

Think about how Sentinel decides to promote a new master.

Multiple Sentinel instances provide fault tolerance by voting to agree on failover decisions. This quorum prevents false failovers.

❓ query_result

intermediate

Sentinel Master Status Query Result

Given three Sentinel instances monitoring a Redis master, what will the SENTINEL masters command return?

Redis

SENTINEL masters

A An error because multiple Sentinels cannot run simultaneously

B A list of all connected clients to the master

C A simple string with the master name only

D A list of dictionaries with details about each monitored master, including name, IP, port, and flags

💡 Hint

Consider what information Sentinel provides about monitored masters.

The SENTINEL masters command returns detailed info about each master monitored by Sentinel instances.

📝 Syntax

advanced

Correct Sentinel Configuration for Multiple Instances

Which configuration snippet correctly sets up three Sentinel instances monitoring the same Redis master?

A

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

B

00001 retsamym tuoemit-revoliaf lenitnes
0005 retsamym sdnocesillim-retfa-nwod lenitnes
2 9736 001.1.861.291 retsamym rotinom lenitnes

C

sentinel monitor mymaster 192.168.1.100 6379 1
sentinel down-after-milliseconds mymaster 5000
sentinel failover-timeout mymaster 10000

D

sentinel monitor mymaster 192.168.1.100 6379 0
sentinel down-after-milliseconds mymaster 5000
sentinel failover-timeout mymaster 10000

💡 Hint

The quorum number must be the minimum number of Sentinels that agree to failover.

The quorum value in sentinel monitor must be at least 2 when running three Sentinels to ensure majority agreement.

❓ optimization

advanced

Optimizing Sentinel Failover Decision Time

You want to reduce the time Sentinel takes to detect a master failure and start failover. Which configuration change helps achieve this without risking false failovers?

A Increase both <code>down-after-milliseconds</code> and <code>failover-timeout</code>

B Increase <code>down-after-milliseconds</code> and decrease <code>failover-timeout</code>

C Decrease both <code>down-after-milliseconds</code> and <code>failover-timeout</code> carefully

D Decrease <code>down-after-milliseconds</code> and increase <code>failover-timeout</code>

💡 Hint

Think about how quickly Sentinel detects failure and how long it waits before failover.

Reducing down-after-milliseconds makes Sentinel detect failure faster; reducing failover-timeout speeds failover start. Both must be balanced to avoid false failovers.

🔧 Debug

expert

Diagnosing Sentinel Failover Failure

You have three Sentinel instances monitoring a Redis master with quorum set to 2. After the master crashes, failover does not occur. What is the most likely cause?

A At least two Sentinels did not detect the master as down, so quorum was not reached

B The master was not configured with <code>replicaof</code> pointing to Sentinels

C The Sentinels were running on the same server, causing network partition

D The <code>failover-timeout</code> was set to zero, disabling failover

💡 Hint

Consider how Sentinel decides to start failover based on quorum.

Failover requires a quorum of Sentinels to agree the master is down. If fewer than quorum detect failure, failover won't start.

Practice

1.

What is the main role of multiple Redis Sentinel instances working together?

easy

A. They monitor the Redis master and agree before failover.

B. They store data backups for Redis.

C. They increase Redis memory capacity.

D. They replace Redis with a different database.

Solution

1. Step 1: Understand Sentinel's purpose

   Redis Sentinel instances monitor the health of Redis masters and replicas.

2. Step 2: Role of multiple Sentinels

   Multiple Sentinels work together to agree on failover decisions to keep Redis available.

3. Final Answer:

   They monitor the Redis master and agree before failover. -> Option A

4. Quick Check:

   Sentinel consensus = monitor and agree [OK]

Hint: Sentinels agree before switching masters [OK]

Common Mistakes:

• Thinking Sentinels store data backups
• Confusing Sentinels with Redis memory management
• Believing Sentinels replace Redis entirely

2.

Which of the following is the correct way to configure multiple Sentinel instances to monitor the same Redis master?

sentinel monitor mymaster 127.0.0.1 6379 2

What does the last number 2 represent?

easy

A. The number of Sentinels required to agree for failover.

B. The port number of the Redis master.

C. The maximum number of replicas allowed.

D. The timeout in seconds for Sentinel responses.

Solution

1. Step 1: Analyze the sentinel monitor command

   The command format is sentinel monitor <name> <ip> <port> <quorum>.

2. Step 2: Understand the quorum parameter

   The last number specifies how many Sentinels must agree to start failover.

3. Final Answer:

   The number of Sentinels required to agree for failover. -> Option A

4. Quick Check:

   Quorum = number of Sentinels to agree [OK]

Hint: Last number in monitor is quorum count [OK]

Common Mistakes:

• Confusing quorum with port number
• Thinking it sets replica count
• Assuming it is a timeout value

3.

Given three Sentinel instances monitoring a Redis master with quorum set to 2, what happens if only one Sentinel detects the master is down?

medium

A. Failover will start immediately.

B. The master will be removed from monitoring.

C. All Sentinels will restart automatically.

D. No failover will occur until at least two Sentinels agree.

Solution

1. Step 1: Understand quorum in failover

   Quorum defines how many Sentinels must agree the master is down before failover.

2. Step 2: Apply quorum to scenario

   With quorum 2, one Sentinel alone cannot trigger failover.

3. Final Answer:

   No failover will occur until at least two Sentinels agree. -> Option D

4. Quick Check:

   Failover needs quorum agreement [OK]

Hint: Failover needs quorum Sentinels agreeing [OK]

Common Mistakes:

• Assuming one Sentinel can trigger failover
• Thinking Sentinels restart automatically
• Believing master is removed without quorum

4.

Identify the error in this Sentinel configuration snippet:

sentinel monitor mymaster 192.168.1.10 6379 0

What is wrong with the quorum value?

medium

A. Port number 6379 is reserved and cannot be used.

B. IP address is invalid for Sentinel monitoring.

C. Quorum cannot be zero; it must be at least 1.

D. The master name 'mymaster' is not allowed.

Solution

1. Step 1: Check quorum parameter rules

   Quorum must be a positive integer, at least 1, to allow failover decisions.

2. Step 2: Analyze given value

   Quorum is set to 0, which is invalid and disables failover agreement.

3. Final Answer:

   Quorum cannot be zero; it must be at least 1. -> Option C

4. Quick Check:

   Quorum ≥ 1 for valid failover [OK]

Hint: Quorum must be positive integer ≥ 1 [OK]

Common Mistakes:

• Setting quorum to zero
• Confusing IP validity with quorum
• Thinking port 6379 is invalid

5.

You have 5 Sentinel instances monitoring a Redis master with quorum set to 3. Two Sentinels lose network connectivity and cannot communicate. What is the impact on failover decisions?

hard

A. Sentinels automatically reduce quorum to 2 to allow failover.

B. Failover can still occur if the remaining 3 Sentinels agree.

C. Failover is impossible because a majority of Sentinels are disconnected.

D. The Redis master will shut down automatically.

Solution

1. Step 1: Understand quorum and Sentinel count

   Quorum is 3, meaning at least 3 Sentinels must agree to failover.

2. Step 2: Analyze network loss impact

   With 5 Sentinels total and 2 disconnected, 3 remain connected and can form quorum.

3. Step 3: Determine failover possibility

   Since 3 Sentinels can still communicate, failover can proceed if they agree.

4. Final Answer:

   Failover can still occur if the remaining 3 Sentinels agree. -> Option B

5. Quick Check:

   Quorum met by connected Sentinels [OK]

Hint: Failover needs quorum Sentinels connected [OK]

Common Mistakes:

• Assuming failover impossible if any Sentinels disconnect
• Thinking quorum auto-adjusts
• Believing Redis master shuts down automatically