Sentinel quorum concept in Redis - Mini Project: Build & Apply

Sentinel Quorum Concept in Redis

📖 Scenario: You are managing a Redis setup that uses Sentinel to monitor the health of Redis master nodes. Sentinel uses a quorum to decide when to failover a master node to a replica. Understanding how to configure and use quorum is important to keep your Redis system reliable.

🎯 Goal: Build a simple Redis Sentinel configuration that sets up a quorum value to control failover decisions.

📋 What You'll Learn

Create a Redis Sentinel configuration dictionary with a master name and its IP and port

Add a quorum value to the Sentinel configuration

Write a command to check the quorum value in the Sentinel configuration

Complete the Sentinel configuration with the quorum setting included

💡 Why This Matters

🌍 Real World

Redis Sentinel uses quorum to decide when to promote a replica to master during failures, ensuring high availability.

💼 Career

Understanding Sentinel quorum is important for roles involving Redis administration, DevOps, and backend infrastructure reliability.

1

Create Sentinel master configuration

Create a dictionary called sentinel_config with the key master_name set to "mymaster", and keys ip and port set to "127.0.0.1" and 6379 respectively.

Redis

# Create the sentinel_config dictionary with master_name, ip, and port
# Your code here

Hint

Use a Python dictionary with keys exactly as master_name, ip, and port.

2

Add quorum setting

Add a key quorum to the sentinel_config dictionary and set its value to 2.

Redis

sentinel_config = {
    "master_name": "mymaster",
    "ip": "127.0.0.1",
    "port": 6379
}
# Add quorum key with value 2 to sentinel_config
# Your code here

Hint

Add the quorum key inside the dictionary with the value 2.

3

Check quorum value

Write a line of code that assigns the quorum value from sentinel_config to a variable called current_quorum.

Redis

sentinel_config = {
    "master_name": "mymaster",
    "ip": "127.0.0.1",
    "port": 6379,
    "quorum": 2
}
# Assign the quorum value to current_quorum
# Your code here

Hint

Use dictionary key access to get the quorum value and assign it to current_quorum.

4

Complete Sentinel configuration with quorum

Ensure the sentinel_config dictionary includes the keys master_name, ip, port, and quorum with the values "mymaster", "127.0.0.1", 6379, and 2 respectively.

Redis

sentinel_config = {
    "master_name": "mymaster",
    "ip": "127.0.0.1",
    "port": 6379,
    "quorum": 2
}
current_quorum = sentinel_config["quorum"]
# Finalize the sentinel_config dictionary
# Your code here

Hint

Check that all keys and values are present in the dictionary as specified.

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