Multiple Sentinel instances in Redis - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a Redis Sentinel instance monitoring the master named 'mymaster'.

Redis

sentinel monitor [1] 127.0.0.1 6379 2

Drag options to blanks, or click blank then click option'

Aredis-master

Bmaster1

Cmymaster

Dprimary

Attempts:

3 left

💡 Hint

Common Mistakes

Using an incorrect master name causes Sentinel not to monitor the right instance.

The sentinel monitor command requires the master name as the first argument. 'mymaster' is the default example name.

2fill in blank

medium

Complete the code to configure the quorum for failover to 3 Sentinel instances.

Redis

sentinel set [1] quorum 3

Drag options to blanks, or click blank then click option'

Afailover

Bmymaster

Cquorum

Dmonitor

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'quorum' or 'failover' as the master name causes configuration errors.

The quorum setting is applied to the master name monitored by Sentinel, here 'mymaster'.

3fill in blank

hard

Fix the error in the command to add a new Sentinel instance to monitor the master 'mymaster'.

Redis

sentinel monitor [1] 127.0.0.1 6379 2

Drag options to blanks, or click blank then click option'

Amymaster

Bmymaster 2

Cmymaster 1

Dmymaster 3

Attempts:

3 left

💡 Hint

Common Mistakes

Appending the quorum number to the master name causes syntax errors.

The sentinel monitor command requires exactly 4 arguments: master name, IP, port, and quorum. The quorum number is missing in the code, so the correct fix is to provide the master name only and add the quorum number after.

4fill in blank

hard

Fill both blanks to configure the failover timeout and parallel sync for 'mymaster'.

Redis

sentinel set [1] failover-timeout [2]

Drag options to blanks, or click blank then click option'

Amymaster

B5000

C10000

Dparallel-syncs

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'parallel-syncs' as a timeout value causes errors.

Using the wrong master name causes configuration to fail.

The first blank is the master name 'mymaster'. The second blank is the failover timeout value in milliseconds, here '10000' (10 seconds).

5fill in blank

hard

Fill all three blanks to create a dictionary of Sentinel instances with their IPs and ports.

Redis

sentinels = [1]: [2], [3]: 26379, '192.168.1.11': 26380}

Drag options to blanks, or click blank then click option'

A'192.168.1.10'

B26379

D26378

Attempts:

3 left

💡 Hint

Common Mistakes

Using integers as keys instead of strings.

Mixing up port numbers for different IPs.

The dictionary keys are IP addresses as strings, and values are port numbers. The first key is '192.168.1.10', the first value is 26378, and the second key is '192.168.1.10' (should be corrected to '192.168.1.11' in code), the second value is 26379.

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