Client discovery through Sentinel in Redis - Step-by-Step Execution

Concept Flow - Client discovery through Sentinel

Client starts

↓

Query Sentinel for master info

↓

Sentinel responds with master address

↓

Client connects to master

↓

If master fails

↓

Sentinel elects new master

↓

Client queries Sentinel again

↓

Client connects to new master

↓

Repeat as needed

Client asks Sentinel for the current master address, connects to it, and if the master changes, repeats the discovery to stay connected to the right server.

Execution Sample

Redis

SENTINEL get-master-addr-by-name mymaster
// Client receives master IP and port
// Client connects to master
// On failover, client queries Sentinel again

Client asks Sentinel for the master address, then connects to that master, updating if Sentinel reports a new master.

Execution Table

Step	Action	Sentinel Response	Client Action	Result
1	Client sends 'SENTINEL get-master-addr-by-name mymaster'	Returns ['192.168.1.10', '6379']	Connect to 192.168.1.10:6379	Connected to master
2	Master fails	Sentinel elects new master '192.168.1.11:6379'	Client sends 'SENTINEL get-master-addr-by-name mymaster' again	Gets new master address
3	Client receives new master address	Returns ['192.168.1.11', '6379']	Connect to 192.168.1.11:6379	Connected to new master
4	No further failover	Sentinel continues monitoring	Client continues normal operations	Stable connection
5	Client stops querying Sentinel	No new info	Client stays connected to last known master	Potential stale connection if failover occurs
6	Exit	N/A	Client disconnects or stops	End of discovery process

💡 Client stops querying Sentinel or disconnects, ending the discovery process

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
master_address	null	192.168.1.10:6379	192.168.1.10:6379 (failed)	192.168.1.11:6379	192.168.1.11:6379

Key Moments - 2 Insights

Why does the client ask Sentinel for the master address again after a failover?

Because the original master failed and Sentinel elected a new master, so the client must get the updated address to connect to the correct server (see execution_table step 2 and 3).

What happens if the client stops querying Sentinel after a failover?

The client may stay connected to the old master address, which is no longer valid, causing errors or stale data (see execution_table step 5).

Visual Quiz - 3 Questions

Look at the execution_table, what master address does the client connect to at Step 1?

A 192.168.1.10:6379

B 192.168.1.11:6379

C 127.0.0.1:6379

D No connection yet

💡 Hint

Check the 'Sentinel Response' and 'Client Action' columns in Step 1.

At which step does the client receive the new master address after failover?

A Step 2

B Step 3

C Step 1

D Step 5

💡 Hint

Look for when the client gets a new address from Sentinel in the table.

If the client never queries Sentinel again after Step 1, what is the likely outcome?

A Client connects to new master automatically

B Sentinel pushes new master info to client

C Client stays connected to old master even if it fails

D Client disconnects immediately

💡 Hint

Refer to Step 5 in the execution_table and variable_tracker for stale connection.

Concept Snapshot

Client discovery through Sentinel:
- Client asks Sentinel for master address using 'SENTINEL get-master-addr-by-name <name>'.
- Sentinel replies with current master IP and port.
- Client connects to that master.
- On failover, Sentinel elects new master.
- Client queries Sentinel again to get updated master address.
- Repeat to maintain connection to correct master.

Full Transcript

Client discovery through Sentinel means the client asks Sentinel for the current master server address. The client sends the command 'SENTINEL get-master-addr-by-name' with the master name. Sentinel responds with the IP and port of the master. The client then connects to that master. If the master fails, Sentinel chooses a new master. The client must ask Sentinel again to get the new master's address and connect to it. This process repeats to keep the client connected to the right master. If the client stops asking Sentinel, it might stay connected to an old master that no longer works.

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