Multiple Sentinel instances in Redis - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of running multiple Redis Sentinel instances?

Multiple Sentinel instances work together to monitor Redis servers, provide high availability, and perform automatic failover if the master server fails.

intermediate

How do multiple Sentinel instances communicate to decide on a failover?

They use a voting system where each Sentinel votes on whether the master is down. When a majority agrees, failover is triggered.

intermediate

Why is it recommended to run an odd number of Sentinel instances?

An odd number helps avoid ties during voting, ensuring clear decisions on failover and reducing split-brain scenarios.

advanced

What happens if a Sentinel instance loses connection to other Sentinels?

It continues monitoring independently but cannot participate in failover decisions until it reconnects with the majority.

beginner

How do multiple Sentinel instances improve Redis system reliability?

They provide redundancy in monitoring and decision-making, so if one Sentinel fails, others still protect the system from downtime.

Why should you run multiple Redis Sentinel instances?

A To ensure high availability and automatic failover

B To increase Redis data storage capacity

C To speed up Redis queries

D To reduce Redis memory usage

Multiple Sentinel instances monitor Redis servers and handle failover to keep the system available.

What is the main reason to have an odd number of Sentinel instances?

A To avoid voting ties during failover decisions

B To balance network traffic

C To reduce CPU usage

D To increase Redis key expiration speed

An odd number prevents ties in voting, ensuring clear failover decisions.

If a Sentinel instance loses connection to others, what happens?

A It immediately triggers failover

B It stops monitoring Redis servers

C It monitors independently but cannot vote

D It deletes Redis data

Disconnected Sentinels keep monitoring but cannot participate in failover voting until reconnected.

How do Sentinels decide a master is down?

A One Sentinel decides alone

B Clients report the master status

C The Redis master sends a shutdown signal

D They use a majority voting system

Sentinels vote, and a majority agreement triggers failover.

What is NOT a benefit of running multiple Sentinel instances?

A Automatic failover

B Increased Redis data storage

C Improved system reliability

D Redundancy in monitoring

Sentinels do not increase data storage; they improve monitoring and failover.

Explain how multiple Redis Sentinel instances work together to provide high availability.

Think about how they decide if the master is down and what happens next.

Why is it important to have an odd number of Sentinel instances in a Redis setup?

Consider how voting works among Sentinels.

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