Monitoring with Sentinel in Redis - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Sentinel Master Discovery Output

You run the command SENTINEL get-master-addr-by-name mymaster on a Redis Sentinel instance monitoring a master named mymaster. What is the expected output format?

A An array with two elements: the IP address and the port of the current master

B A string with the master name only

C An integer representing the number of connected slaves

D A boolean indicating if the master is reachable

💡 Hint

Think about what information Sentinel needs to provide to clients about the master.

The SENTINEL get-master-addr-by-name command returns the IP and port of the master as an array of two elements. This helps clients connect to the current master.

🧠 Conceptual

intermediate

Sentinel Quorum Role

What is the role of the quorum setting in Redis Sentinel configuration?

A It sets the maximum number of slaves allowed per master

B It controls the frequency of Sentinel health checks

C It specifies the timeout for client connections to the master

D It defines the minimum number of Sentinels that must agree a master is down before failover

💡 Hint

Quorum is about agreement among Sentinels.

The quorum setting ensures that a failover only happens if enough Sentinels agree the master is unreachable, preventing false failovers.

❓ Troubleshoot

advanced

Sentinel Failover Not Triggering

You notice that your Redis Sentinel setup is not triggering failover even though the master is down. Which configuration mistake could cause this?

A The master node has more than 5 connected slaves

B The quorum value is set higher than the number of running Sentinel instances

C The Sentinel port is set to the same port as the Redis master

D The client timeout is set to 1000 milliseconds

💡 Hint

Failover depends on enough Sentinels agreeing the master is down.

If quorum is higher than the number of Sentinels running, failover will never trigger because the required agreement can't be reached.

🔀 Workflow

advanced

Sentinel Automatic Failover Steps

Put the following Redis Sentinel failover steps in the correct order.

A 1,3,2,4

B 2,1,3,4

C 1,2,3,4

D 3,1,2,4

💡 Hint

Think about detection, agreement, promotion, then update.

The failover process starts with detection, then quorum agreement, then slave promotion, and finally updating slaves to follow the new master.

✅ Best Practice

expert

Sentinel Deployment Best Practice

Which is the best practice for deploying Redis Sentinel instances to ensure high availability and avoid split-brain scenarios?

A Deploy an odd number of Sentinel instances on separate physical or virtual machines across different failure domains.

B Deploy all Sentinel instances on the same machine as the Redis master for faster communication.

C Deploy Sentinel instances only on slave nodes to reduce load on the master.

D Deploy a single Sentinel instance with a very low quorum value to speed up failover.

💡 Hint

Think about avoiding single points of failure and ensuring consensus.

Deploying an odd number of Sentinels across different machines and failure domains helps achieve reliable quorum and prevents split-brain.