Sentinel quorum concept in Redis - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Sentinel Quorum

In Redis Sentinel, what does the quorum value represent?

A The number of replicas that must be synchronized with the master

B The minimum number of Sentinels that must agree a master is down before failover starts

C The maximum number of clients that can connect to the master

D The total number of Redis nodes in the cluster

💡 Hint

Think about how Sentinels decide to promote a new master.

The quorum is the count of Sentinels that must agree a master is unreachable before failover begins. This prevents false failovers.

❓ query_result

intermediate

Sentinel Quorum Check Result

Given a Redis Sentinel setup with 5 Sentinels and quorum set to 3, what will happen if only 2 Sentinels report the master as down?

A Sentinel will restart the master node

B Failover will start immediately

C Failover will not start because quorum is not reached

D All Sentinels will disconnect from the master

💡 Hint

Quorum means minimum agreement needed.

Failover requires at least quorum number of Sentinels to agree the master is down. With only 2 out of 5, quorum 3 is not met, so no failover.

📝 Syntax

advanced

Correct Sentinel Configuration for Quorum

Which Redis Sentinel configuration line correctly sets the quorum to 4 for a master named 'mymaster'?

A quorum sentinel mymaster 4

B sentinel mymaster quorum 4

C sentinel mymaster 4 quorum

D sentinel quorum mymaster 4

💡 Hint

The correct order is sentinel quorum, master name, then value.

The correct syntax is sentinel quorum <master-name> <number>. Option D follows this format.

❓ optimization

advanced

Optimizing Sentinel Quorum for Reliability

You have 7 Sentinels monitoring a Redis master. To balance between fast failover and avoiding false positives, which quorum value is best?

A 4

B 1

C 7

D 2

💡 Hint

Quorum should be a majority but not all Sentinels.

Setting quorum to 4 (a majority of 7) ensures enough Sentinels agree before failover, reducing false positives but allowing timely failover.

🔧 Debug

expert

Diagnosing Failover Failure Due to Quorum

In a Redis Sentinel cluster with 3 Sentinels and quorum set to 2, failover never triggers even though the master is down. What is the most likely cause?

A One Sentinel is not reachable, so only 2 Sentinels remain and quorum is not met

B Quorum is set too low, causing failover to be disabled

C The master is not actually down, so Sentinels do not agree

D Sentinel quorum must be equal to the total number of Sentinels

💡 Hint

Check Sentinel connectivity and quorum requirements.

If one Sentinel is unreachable, only 2 Sentinels remain active. With quorum 2, both must agree. If one is down or disconnected, quorum cannot be reached, so failover won't trigger.

Practice

1.

What does the quorum setting in Redis Sentinel control?

easy

A. The maximum number of clients connected to Redis

B. The number of replicas a master must have

C. The timeout duration for client connections

D. The number of Sentinels that must agree a master is down before failover

Solution

1. Step 1: Understand Sentinel quorum purpose

   The quorum defines how many Sentinels must agree that the master is down before starting failover.

2. Step 2: Eliminate unrelated options

   Options about clients, timeouts, or replicas do not relate to quorum.

3. Final Answer:

   The number of Sentinels that must agree a master is down before failover -> Option D

4. Quick Check:

   Sentinel quorum = agreement count [OK]

Hint: Quorum means how many Sentinels agree on failure [OK]

Common Mistakes:

• Confusing quorum with client limits
• Thinking quorum is a timeout setting
• Mixing quorum with replica count

2.

Which of the following is the correct way to set the quorum to 3 in a Redis Sentinel configuration file?

sentinel monitor mymaster 127.0.0.1 6379 3

easy

A. sentinel set quorum 3

B. sentinel quorum mymaster 3

C. sentinel monitor mymaster 127.0.0.1 6379 3

D. sentinel quorum 3 mymaster

Solution

1. Step 1: Recall correct sentinel monitor syntax

   The sentinel monitor command includes the master name, IP, port, and quorum number at the end.

2. Step 2: Match options to syntax

   Only sentinel monitor mymaster 127.0.0.1 6379 3 matches the full correct syntax with quorum as the last argument.

3. Final Answer:

   sentinel monitor mymaster 127.0.0.1 6379 3 -> Option C

4. Quick Check:

   Monitor command ends with quorum number [OK]

Hint: Quorum is last number in sentinel monitor command [OK]

Common Mistakes:

• Using 'sentinel quorum' command which does not exist
• Placing quorum before IP or port
• Confusing 'set' command with monitor

3.

Given 5 Sentinels monitoring a master with quorum set to 3, what happens if only 2 Sentinels report the master as down?

medium

A. Failover starts immediately

B. Failover does not start because quorum is not reached

C. All Sentinels restart

D. The master is removed from monitoring

Solution

1. Step 1: Understand quorum requirement

   Quorum is 3, meaning at least 3 Sentinels must agree the master is down to start failover.

2. Step 2: Analyze 2 Sentinels reporting down

   Since only 2 Sentinels report down, quorum is not met, so failover will not start.

3. Final Answer:

   Failover does not start because quorum is not reached -> Option B

4. Quick Check:

   Quorum unmet = no failover [OK]

Hint: Failover needs quorum Sentinels agreeing [OK]

Common Mistakes:

• Assuming failover starts with any Sentinel down report
• Thinking Sentinels restart on partial failure
• Believing master is removed automatically

4.

You configured 4 Sentinels with quorum set to 3, but failover never happens even when the master is down. What is the most likely cause?

medium

A. Quorum is set higher than the number of Sentinels available

B. Sentinel IP addresses are incorrect

C. The master is not actually down

D. The Redis version does not support Sentinel

Solution

1. Step 1: Check quorum vs Sentinels count

   Quorum is 3 but only 4 Sentinels exist; if some Sentinels are unreachable, quorum may not be met.

2. Step 2: Identify cause of failover not triggering

   If quorum is effectively higher than reachable Sentinels, failover won't start.

3. Final Answer:

   Quorum is set higher than the number of Sentinels available -> Option A

4. Quick Check:

   Quorum > available Sentinels blocks failover [OK]

Hint: Quorum must be ≤ number of active Sentinels [OK]

Common Mistakes:

• Ignoring Sentinel network issues
• Assuming master is always down
• Blaming Redis version without checking

5.

You have 7 Sentinels monitoring a Redis master. To ensure high availability, you want failover to start only if a majority agrees the master is down. What is the best quorum value to set?

hard

A. 4

B. 3

C. 5

D. 7

Solution

1. Step 1: Calculate majority of 7 Sentinels

   Majority means more than half, so (7 / 2) = 3.5, rounded up to 4.

2. Step 2: Choose quorum equal to majority

   Setting quorum to 4 ensures failover starts only if most Sentinels agree.

3. Final Answer:

   4 -> Option A

4. Quick Check:

   Majority quorum = 4 for 7 Sentinels [OK]

Hint: Quorum = majority of Sentinels (half + 1) [OK]

Common Mistakes:

• Setting quorum less than half
• Setting quorum equal to total Sentinels
• Not rounding up majority