Client discovery through Sentinel in Redis - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to get the master address from Sentinel.

Redis

redis-cli -p 26379 sentinel get-master-addr-by-name [1]

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

Aprimary

Bmaster1

Credis-master

Dmymaster

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong master name that Sentinel does not recognize.

Forgetting to specify the master name argument.

The default master name in Sentinel configuration is mymaster. This command asks Sentinel for the current master address.

2fill in blank

medium

Complete the command to check the number of Sentinel monitors.

Redis

redis-cli -p 26379 sentinel [1]

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

Asentinels

Bslaves

Cmasters

Dget-master-addr-by-name

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'slaves' instead of 'masters' to list masters.

Using 'sentinels' which lists Sentinel instances, not masters.

The masters command lists all masters monitored by Sentinel, which helps check how many masters are monitored.

3fill in blank

hard

Fix the error in the command to list slaves of a master.

Redis

redis-cli -p 26379 sentinel [1] mymaster

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

Aget-slaves

Bslaves

Cslave

Dlist-slaves

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular form 'slave' which is not a valid command.

Using made-up commands like 'get-slaves' or 'list-slaves'.

The correct Sentinel command to list slaves of a master is slaves. Other options are invalid commands.

4fill in blank

hard

Fill both blanks to create a command that lists all Sentinel instances monitoring the master.

Redis

redis-cli -p 26379 sentinel [1] [2]

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

Asentinels

Bmymaster

Cmaster1

Dmasters

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'masters' instead of 'sentinels' for the first blank.

Using a wrong master name in the second blank.

The command sentinels mymaster lists all Sentinel instances monitoring the master named 'mymaster'.

5fill in blank

hard

Fill all three blanks to create a command that gets the master address by name on a custom Sentinel port.

Redis

redis-cli -p [1] sentinel [2] [3]

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

A26379

Bget-master-addr-by-name

Cmymaster

Dmasters

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong port number.

Using 'masters' instead of 'get-master-addr-by-name' command.

Using an incorrect master name.

This command connects to Sentinel on port 26379 and asks for the master address of mymaster using the get-master-addr-by-name command.

Practice

1. What is the main purpose of Redis Sentinel in client discovery?

easy

A. To automatically find the current Redis master server

B. To store data persistently on disk

C. To increase the speed of Redis commands

D. To backup Redis data to the cloud

Solution

1. Step 1: Understand Sentinel's role and compare options

   Redis Sentinel monitors Redis servers and helps clients find the current master automatically. Only To automatically find the current Redis master server describes this discovery role; others describe unrelated features.

2. Final Answer:

   To automatically find the current Redis master server -> Option A

3. Quick Check:

   Sentinel = master discovery [OK]

Hint: Sentinel helps clients find the master automatically [OK]

Common Mistakes:

• Confusing Sentinel with data storage
• Thinking Sentinel speeds up commands
• Assuming Sentinel handles backups

2. Which Redis command is used to get the current master address from Sentinel?

easy

A. SENTINEL get-master

B. SENTINEL get-master-addr-by-name

C. SENTINEL find-master

D. SENTINEL master-address

Solution

1. Step 1: Recall the correct command syntax and verify options

   The official Redis command to get master address is SENTINEL get-master-addr-by-name. Only SENTINEL get-master-addr-by-name matches the exact command; others are incorrect or invalid.

2. Final Answer:

   SENTINEL get-master-addr-by-name <master-name> -> Option B

3. Quick Check:

   Command = SENTINEL get-master-addr-by-name [OK]

Hint: Remember full command: SENTINEL get-master-addr-by-name [OK]

Common Mistakes:

• Using incomplete or wrong command names
• Omitting 'get-master-addr-by-name'
• Confusing with other Sentinel commands

3. Given the command SENTINEL get-master-addr-by-name mymaster returns ["192.168.1.10", "6379"], what does this output represent?

medium

A. The IP and port of the Sentinel server

B. The IP and port of a Redis slave server

C. The IP and port of the current Redis master named 'mymaster'

D. An error message indicating master not found

Solution

1. Step 1: Understand the command output and match output meaning

   The command returns a two-element array: IP address and port of the master. Since the command queries the master by name, the output is the master's IP and port.

2. Final Answer:

   The IP and port of the current Redis master named 'mymaster' -> Option C

3. Quick Check:

   Output = master IP and port [OK]

Hint: Output array = [master IP, master port] [OK]

Common Mistakes:

• Confusing master with slave address
• Thinking output is Sentinel info
• Assuming output is an error

4. You run SENTINEL get-master-addr-by-name mymaster but get an empty array []. What is the most likely cause?

medium

A. The Redis server is down

B. The client is connected to a Redis slave

C. The command syntax is incorrect

D. The Sentinel does not know about a master named 'mymaster'

Solution

1. Step 1: Interpret empty array result and check possible reasons

   An empty array means Sentinel has no info on the requested master name. If the master name is unknown to Sentinel, it returns empty; syntax errors cause errors, not empty arrays.

2. Final Answer:

   The Sentinel does not know about a master named 'mymaster' -> Option D

3. Quick Check:

   Empty array = unknown master name [OK]

Hint: Empty array means unknown master name to Sentinel [OK]

Common Mistakes:

• Assuming Redis server down causes empty array
• Thinking syntax error returns empty array
• Confusing slave connection with empty result

5. You want your application to automatically connect to the current Redis master even if failover happens. Which approach using Sentinel is best?

hard

A. Use SENTINEL get-master-addr-by-name to fetch master IP and port dynamically before connecting

B. Hardcode the master IP and port in your app configuration

C. Connect directly to a Redis slave and promote it manually if needed

D. Use Redis CLI to manually check master and update app config

Solution

1. Step 1: Understand automatic master discovery and evaluate other options

   Using Sentinel's command to get the master address dynamically allows the app to adapt to failovers. Hardcoding IP/port or manual checks do not handle failover automatically; connecting to slaves is not reliable for writes.

2. Final Answer:

   Use SENTINEL get-master-addr-by-name to fetch master IP and port dynamically before connecting -> Option A

3. Quick Check:

   Dynamic master discovery = best practice [OK]

Hint: Always fetch master address dynamically via Sentinel [OK]

Common Mistakes:

• Hardcoding master address ignoring failover
• Connecting to slaves for writes
• Manual updates instead of automatic discovery