Client discovery through Sentinel in Redis - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Redis Sentinel used for in client discovery?

Redis Sentinel helps clients find the current master node automatically by monitoring Redis servers and providing the master address when requested.

beginner

How does a Redis client discover the master node using Sentinel?

The client queries Sentinel with the command SENTINEL get-master-addr-by-name <master-name> to get the current master's IP and port.

intermediate

What happens if the master node fails in a Redis Sentinel setup?

Sentinel automatically promotes a slave to master and updates its state. Clients querying Sentinel will then get the new master's address for continued operations.

intermediate

Why is client discovery through Sentinel better than hardcoding master addresses?

Because Sentinel provides dynamic discovery, clients don’t need manual updates when failover happens, making the system more reliable and easier to maintain.

beginner

Which Redis command do clients use to ask Sentinel for the master address?

Clients use SENTINEL get-master-addr-by-name <master-name> to get the current master's IP and port.

What does Redis Sentinel provide to clients for discovery?

A A list of all slave nodes

B The current master node address

C The Redis configuration file

D The client connection pool size

Sentinel provides the current master node address so clients can connect to the right server.

Which command does a Redis client use to get the master address from Sentinel?

A CONFIG GET master

B SENTINEL slaves <master-name>

C INFO replication

D SENTINEL get-master-addr-by-name <master-name>

The command SENTINEL get-master-addr-by-name returns the current master's IP and port.

What happens when the master fails in a Sentinel-managed Redis setup?

A Sentinel deletes all data

B Clients must manually reconnect to a new master

C Sentinel promotes a slave to master automatically

D The Redis server shuts down

Sentinel automatically promotes a slave to master to keep the system running.

Why should clients use Sentinel for discovery instead of hardcoding the master address?

A To handle failover automatically

B To reduce network traffic

C To increase Redis memory

D To avoid using Redis commands

Using Sentinel allows clients to automatically find the new master after failover.

Which of these is NOT a role of Redis Sentinel?

A Client connection pooling

B Automatic failover

C Monitoring Redis servers

D Providing master address to clients

Sentinel does not manage client connection pools; it monitors and manages failover.

Explain how Redis Sentinel helps clients discover the current master node.

Think about how clients avoid hardcoding addresses.

Describe what happens during a failover in a Redis Sentinel environment and how clients adapt.

Focus on the automatic promotion and client discovery process.

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