Sentinel configuration in Redis - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the name of the monitored master in the Sentinel configuration.

Redis

sentinel monitor [1] 127.0.0.1 6379 2

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

Amymaster

Bmaster1

Credis-master

Dprimary

Attempts:

3 left

💡 Hint

Common Mistakes

Using IP address instead of a name

Using a name with spaces

Omitting the master name

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

2fill in blank

medium

Complete the code to set the quorum for the Sentinel to 3.

Redis

sentinel set [1] quorum 3

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

Aredis-master

Bmaster1

Cprimary

Dmymaster

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong master name

Setting quorum without specifying master name

Confusing quorum number with master name

The quorum setting applies to the monitored master name. It tells Sentinel how many Sentinels must agree to failover.

3fill in blank

hard

Fix the error in the Sentinel configuration command to set the failover timeout to 15000 milliseconds.

Redis

sentinel set mymaster [1] 15000

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

Afailovertimeout

Bfailover_timeout

Cfailover-timeout

DfailoverTimeout

Attempts:

3 left

💡 Hint

Common Mistakes

Using underscores instead of hyphens

Using camelCase

Misspelling the option name

The correct option name is failover-timeout with a hyphen, as required by Redis Sentinel configuration syntax.

4fill in blank

hard

Fill both blanks to configure Sentinel to notify a script and set the client reconfiguration timeout.

Redis

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

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

Anotification-script

Bclient-reconfig-script

Cclient-reconfig-timeout

Dnotification-timeout

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up script and timeout options

Using incorrect option names

Using underscores instead of hyphens

The notification-script option sets the script to run on events. The client-reconfig-timeout sets the timeout for client reconfiguration.

5fill in blank

hard

Fill all three blanks to configure Sentinel with master name, IP, port, and quorum.

Redis

sentinel monitor [1] [2] [3] 2

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

Amymaster

B192.168.1.100

C6379

Dlocalhost

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping IP and port positions

Using 'localhost' instead of IP address

Using wrong master name

The sentinel monitor command requires the master name, IP address, port, and quorum number. Here, 'mymaster' is the name, '192.168.1.100' is the IP, and '6379' is the port.

Practice

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

easy

A. To provide a graphical user interface for Redis

B. To store data persistently on disk

C. To monitor Redis servers and perform automatic failover if the master fails

D. To increase the speed of Redis queries

Solution

1. Step 1: Understand Sentinel's role

   Redis Sentinel monitors Redis servers to detect failures.

2. Step 2: Identify failover capability

   Sentinel automatically switches to a backup server if the master fails.

3. Final Answer:

   To monitor Redis servers and perform automatic failover if the master fails -> Option C

4. Quick Check:

   Sentinel = automatic failover [OK]

Hint: Sentinel watches and switches masters automatically [OK]

Common Mistakes:

• Confusing Sentinel with data storage
• Thinking Sentinel speeds up queries
• Assuming Sentinel provides UI

2. Which of the following is the correct syntax to configure a Redis Sentinel to monitor a master named mymaster on IP 192.168.1.100 and port 6379?

easy

A. sentinel monitor mymaster 192.168.1.100 6379 2

B. monitor sentinel mymaster 192.168.1.100 6379 2

C. sentinel set mymaster 192.168.1.100 6379 2

D. sentinel watch mymaster 192.168.1.100 6379 2

Solution

1. Step 1: Recall Sentinel monitor command format

   The correct command starts with sentinel monitor followed by master name, IP, port, and quorum.

2. Step 2: Match the correct syntax

   sentinel monitor mymaster 192.168.1.100 6379 2 matches the correct order and keywords.

3. Final Answer:

   sentinel monitor mymaster 192.168.1.100 6379 2 -> Option A

4. Quick Check:

   sentinel monitor = correct syntax [OK]

Hint: Sentinel monitor command starts with 'sentinel monitor' [OK]

Common Mistakes:

• Swapping 'monitor' and 'sentinel'
• Using 'set' or 'watch' instead of 'monitor'
• Incorrect order of parameters

3. Given the following Sentinel configuration snippet:

sentinel monitor mymaster 10.0.0.1 6379 2
sentinel down-after-milliseconds mymaster 5000
sentinel failover-timeout mymaster 60000

What does the down-after-milliseconds setting specify?

medium

A. The time Sentinel waits before declaring the master as down

B. The time Redis waits before accepting writes

C. The timeout for client connections to Redis

D. The time Sentinel waits before starting a failover

Solution

1. Step 1: Understand 'down-after-milliseconds'

   This setting defines how long Sentinel waits to consider the master unreachable.

2. Step 2: Differentiate from failover timeout

   Failover timeout is different; it controls failover duration, not detection.

3. Final Answer:

   The time Sentinel waits before declaring the master as down -> Option A

4. Quick Check:

   down-after-milliseconds = detection wait time [OK]

Hint: 'down-after-milliseconds' means detection delay [OK]

Common Mistakes:

• Confusing with failover timeout
• Thinking it affects client connections
• Assuming it controls Redis write delay

4. You have this Sentinel configuration line:

sentinel monitor mymaster 10.0.0.1 6379

What is wrong with this configuration?

medium

A. IP address format is incorrect

B. Master name should be 'master' not 'mymaster'

C. Port number should be 6380 for Sentinel

D. Missing the quorum number at the end

Solution

1. Step 1: Check required parameters for sentinel monitor

   The command requires master name, IP, port, and quorum number.

2. Step 2: Identify missing quorum

   The quorum number (minimum votes to failover) is missing in the line.

3. Final Answer:

   Missing the quorum number at the end -> Option D

4. Quick Check:

   Quorum number required in sentinel monitor [OK]

Hint: Sentinel monitor needs quorum number last [OK]

Common Mistakes:

• Ignoring quorum number
• Changing port unnecessarily
• Assuming master name must be 'master'

5. You want to configure Redis Sentinel to monitor a master and automatically failover if it is down. Which combination of settings is necessary to ensure Sentinel detects failure quickly and performs failover within 1 minute?

hard

A. Set down-after-milliseconds to 60000 only

B. Set down-after-milliseconds to 5000 and failover-timeout to 60000

C. Set failover-timeout to 5000 only

D. Set down-after-milliseconds to 60000 and failover-timeout to 5000

Solution

1. Step 1: Understand 'down-after-milliseconds'

   This controls how fast Sentinel marks master as down; 5000 ms means 5 seconds.

2. Step 2: Understand 'failover-timeout'

   This controls how long failover can take; 60000 ms means 60 seconds (1 minute).

3. Step 3: Combine settings for quick detection and failover

   Setting down-after-milliseconds to 5000 and failover-timeout to 60000 ensures detection in 5 seconds and failover within 1 minute.

4. Final Answer:

   Set down-after-milliseconds to 5000 and failover-timeout to 60000 -> Option B

5. Quick Check:

   Fast detection + 1 min failover = Set down-after-milliseconds to 5000 and failover-timeout to 60000 [OK]

Hint: Fast detection needs low down-after; failover-timeout sets max failover time [OK]

Common Mistakes:

• Swapping values of down-after and failover-timeout
• Setting only one parameter
• Using too high down-after-milliseconds