Sentinel architecture in Redis - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

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

Redis

sentinel monitor [1] 127.0.0.1 6379 2

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

Aredis1

Bslave1

Cmymaster

Dmaster1

Attempts:

3 left

💡 Hint

Common Mistakes

Using a slave or random name instead of the master name.

Confusing the IP address with the master name.

The sentinel monitor command requires the master name to monitor. 'mymaster' is the default example name.

2fill in blank

medium

Complete the code to configure the quorum for Sentinel to agree on a failover.

Redis

sentinel monitor mymaster 127.0.0.1 6379 [1]

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

A3

B2

C1

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Setting quorum to 0 disables failover detection.

Setting quorum too high causes failover never to trigger.

The quorum number defines how many Sentinels need to agree a master is down before failover starts. Usually, 2 or more is recommended.

3fill in blank

hard

Fix the error in the Sentinel failover command to trigger failover for 'mymaster'.

Redis

sentinel failover [1]

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

Amymaster

Bredis-master

Cslave1

Dmaster-1

Attempts:

3 left

💡 Hint

Common Mistakes

Using a slave or incorrect master name causes command failure.

Typo in the master name leads to no failover.

The failover command requires the exact master name monitored by Sentinel. 'mymaster' is the correct master name here.

4fill in blank

hard

Fill both blanks to configure Sentinel to notify a script and set the down-after-milliseconds timeout.

Redis

sentinel [1] mymaster /path/to/notify.sh
sentinel [2] mymaster 5000

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

Anotification-script

Bdown-after-milliseconds

Cclient-reconfig-script

Dfailover-timeout

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up script and timeout commands.

Using wrong command names causes Sentinel to ignore settings.

notification-script sets a script to run on events.
down-after-milliseconds sets how long Sentinel waits before marking master as down.

5fill in blank

hard

Fill all three blanks to create a Sentinel configuration snippet that sets the failover timeout, parallel syncs, and client reconfiguration script.

Redis

sentinel [1] mymaster 60000
sentinel [2] mymaster 1
sentinel [3] mymaster /path/to/reconfig.sh

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

Afailover-timeout

Bparallel-syncs

Cclient-reconfig-script

Ddown-after-milliseconds

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing down-after-milliseconds with failover-timeout.

Using notification-script instead of client-reconfig-script.

failover-timeout sets max time for failover.
parallel-syncs sets how many slaves can sync at once.
client-reconfig-script sets script to reconfigure clients after failover.

Practice

1. What is the main purpose of Redis Sentinel in a Redis setup?

easy

A. To compress Redis data for faster transmission

B. To store large amounts of data persistently

C. To monitor Redis servers and automatically handle failover

D. To provide a graphical user interface for Redis

Solution

1. Step 1: Understand Sentinel's role

   Redis Sentinel monitors Redis servers to detect failures.

2. Step 2: Identify Sentinel's key feature

   It automatically switches to a backup server if the main one fails, ensuring availability.

3. Final Answer:

   To monitor Redis servers and automatically handle failover -> Option C

4. Quick Check:

   Sentinel = automatic failover [OK]

Hint: Sentinel watches servers and switches on failure [OK]

Common Mistakes:

• Confusing Sentinel with data storage
• Thinking Sentinel provides UI
• Assuming Sentinel compresses data

2. Which of the following is the correct way to start a Redis Sentinel instance using the command line?

easy

A. redis-sentinel /path/to/sentinel.conf

B. redis-server --sentinel /path/to/sentinel.conf

C. redis-cli sentinel start /path/to/sentinel.conf

D. redis-start sentinel /path/to/sentinel.conf

Solution

1. Step 1: Recall Redis Sentinel startup command

   The correct command to start Sentinel is redis-sentinel followed by the config file.

2. Step 2: Check each option

   redis-sentinel /path/to/sentinel.conf matches the correct syntax; others are invalid commands or flags.

3. Final Answer:

   redis-sentinel /path/to/sentinel.conf -> Option A

4. Quick Check:

   Sentinel starts with redis-sentinel command [OK]

Hint: Sentinel uses redis-sentinel command, not redis-server [OK]

Common Mistakes:

• Using redis-server with --sentinel flag
• Trying to start Sentinel via redis-cli
• Using non-existent redis-start command

3. Given a Redis Sentinel setup monitoring a master named mymaster, what will the command redis-cli -p 26379 SENTINEL get-master-addr-by-name mymaster return?

medium

A. The configuration file path of Sentinel

B. The IP and port of the current master server

C. The list of all slaves under the master

D. An error because the command is invalid

Solution

1. Step 1: Understand the command purpose

   The command queries Sentinel on port 26379 for the address of the master named 'mymaster'.

2. Step 2: Identify expected output

   It returns the IP and port of the current master server Sentinel monitors.

3. Final Answer:

   The IP and port of the current master server -> Option B

4. Quick Check:

   get-master-addr-by-name returns master address [OK]

Hint: get-master-addr-by-name returns master IP and port [OK]

Common Mistakes:

• Confusing master address with slave list
• Expecting config file path as output
• Assuming command is invalid

4. You configured Redis Sentinel but it never triggers failover when the master goes down. Which of the following is the most likely cause?

medium

A. Sentinel quorum is not reached due to insufficient Sentinel instances

B. The master server has persistence disabled

C. The Redis version is too new for Sentinel

D. The client application does not use SSL

Solution

1. Step 1: Understand failover conditions

   Sentinel requires a quorum of Sentinel instances to agree before failover.

2. Step 2: Analyze the cause of no failover

   If quorum is not reached, Sentinel will not promote a slave to master.

3. Final Answer:

   Sentinel quorum is not reached due to insufficient Sentinel instances -> Option A

4. Quick Check:

   Failover needs quorum agreement [OK]

Hint: Failover needs quorum; check Sentinel count [OK]

Common Mistakes:

• Blaming persistence for failover
• Assuming Redis version blocks Sentinel
• Thinking SSL affects failover

5. In a Redis Sentinel cluster with 5 Sentinel nodes monitoring 3 Redis masters, how many Sentinel nodes must agree to trigger a failover for a master if the quorum is set to 3?

hard

A. At least 2 Sentinel nodes must agree

B. Only 1 Sentinel node needs to agree

C. All 5 Sentinel nodes must agree

D. At least 3 Sentinel nodes must agree

Solution

1. Step 1: Understand quorum setting

   The quorum setting defines the minimum number of Sentinels that must agree to start failover.

2. Step 2: Apply quorum to the cluster

   With quorum set to 3, at least 3 Sentinel nodes must agree to trigger failover.

3. Final Answer:

   At least 3 Sentinel nodes must agree -> Option D

4. Quick Check:

   Quorum = minimum agreeing Sentinels [OK]

Hint: Quorum number = minimum Sentinels needed for failover [OK]

Common Mistakes:

• Thinking only 1 Sentinel is enough
• Assuming all Sentinels must agree
• Confusing quorum with total Sentinel count