Bird
Raised Fist0
Redisquery~30 mins

Multiple Sentinel instances in Redis - Mini Project: Build & Apply

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime
Managing Multiple Redis Sentinel Instances
📖 Scenario: You are managing a Redis setup that uses Sentinel for high availability. To ensure reliability, you want to configure multiple Sentinel instances monitoring the same Redis master server.
🎯 Goal: Set up configuration data for three Redis Sentinel instances monitoring one Redis master server. Then, write a query to list all Sentinel instances monitoring the master, and finally add a command to check the master status from one Sentinel.
📋 What You'll Learn
Create a Redis hash called sentinel:master with the master server details.
Create three Redis hashes called sentinel:instance:1, sentinel:instance:2, and sentinel:instance:3 with Sentinel instance details.
Add a Redis set called sentinel:instances containing the keys of all Sentinel instances.
Write a Redis command to retrieve all Sentinel instances monitoring the master.
Write a Redis command to check the master status from Sentinel instance 1.
💡 Why This Matters
🌍 Real World
In real-world Redis deployments, multiple Sentinel instances monitor the master to provide high availability and automatic failover.
💼 Career
Understanding how to configure and query multiple Sentinel instances is important for roles like DevOps engineers, system administrators, and backend developers managing Redis clusters.
Progress0 / 4 steps
1
Create Redis hash for the master server
Create a Redis hash called sentinel:master with these fields and values: ip set to 192.168.1.100, port set to 6379, and name set to mymaster.
Redis
Hint

Use the HSET command to create a hash with multiple fields.

2
Create Redis hashes for three Sentinel instances and a set of instances
Create three Redis hashes called sentinel:instance:1, sentinel:instance:2, and sentinel:instance:3. Each should have fields ip and port with these values respectively: (1) 192.168.1.101, 26379; (2) 192.168.1.102, 26379; (3) 192.168.1.103, 26379. Then create a Redis set called sentinel:instances containing the keys of these three Sentinel hashes.
Redis
Hint

Use HSET for each Sentinel instance and SADD to add all instance keys to the set.

3
Retrieve all Sentinel instances monitoring the master
Write a Redis command to get all members of the set sentinel:instances, which lists all Sentinel instance keys monitoring the master.
Redis
Hint

Use the SMEMBERS command to list all members of a set.

4
Check master status from Sentinel instance 1
Write a Redis Sentinel command to check the master status from Sentinel instance 1 by using SENTINEL get-master-addr-by-name mymaster.
Redis
Hint

Use the SENTINEL get-master-addr-by-name command with the master name.

Practice

(1/5)
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
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard