Client discovery through Sentinel in Redis - Mini Project: Build & Apply

Client Discovery through Redis Sentinel

📖 Scenario: You are managing a Redis setup with Sentinel for high availability. Your application needs to discover the current master node automatically to send write commands.Redis Sentinel monitors Redis masters and their replicas, and provides the current master address to clients.

🎯 Goal: Build a simple Redis Sentinel client discovery setup that queries Sentinel to find the current master address.

📋 What You'll Learn

Create a list of Sentinel nodes with their IPs and ports

Define the name of the monitored master

Query Sentinel nodes to get the current master address

Store the master address for client use

💡 Why This Matters

🌍 Real World

Redis Sentinel is used in production to provide automatic failover and high availability. Applications need to discover the current master to send writes correctly.

💼 Career

Knowing how to interact with Redis Sentinel is important for backend developers and DevOps engineers managing scalable Redis deployments.

1

Setup Sentinel nodes list

Create a list called sentinel_nodes containing these exact tuples: ("192.168.1.10", 26379), ("192.168.1.11", 26379), and ("192.168.1.12", 26379) representing the Sentinel IP addresses and ports.

Redis

# Your code here

Hint

Use a Python list with tuples for IP and port pairs.

2

Define monitored master name

Create a string variable called master_name and set it exactly to "mymaster", which is the name Sentinel uses to monitor the master Redis instance.

Redis

sentinel_nodes = [("192.168.1.10", 26379), ("192.168.1.11", 26379), ("192.168.1.12", 26379)]
# Your code here

Hint

Assign the exact string "mymaster" to master_name.

3

Query Sentinel for master address

Write a function called get_master_address that takes sentinel_nodes and master_name as parameters. Inside, use a for loop with variables ip and port to iterate over sentinel_nodes. For each Sentinel, connect using redis.StrictRedis(host=ip, port=port), then call sentinel_client.sentinel_get_master_addr_by_name(master_name). Return the first non-None master address found as a tuple (master_ip, master_port). If none found, return None.

Redis

sentinel_nodes = [("192.168.1.10", 26379), ("192.168.1.11", 26379), ("192.168.1.12", 26379)]
master_name = "mymaster"

# Your code here

Hint

Use a for loop with ip, port to connect to each Sentinel and call sentinel_get_master_addr_by_name.

4

Store the discovered master address

Call the function get_master_address with sentinel_nodes and master_name, and assign the result to a variable called current_master. This variable will hold the tuple (master_ip, master_port) for client use.

Redis

import redis

sentinel_nodes = [("192.168.1.10", 26379), ("192.168.1.11", 26379), ("192.168.1.12", 26379)]
master_name = "mymaster"

def get_master_address(sentinel_nodes, master_name):
    for ip, port in sentinel_nodes:
        sentinel_client = redis.StrictRedis(host=ip, port=port)
        master = sentinel_client.sentinel_get_master_addr_by_name(master_name)
        if master is not None:
            return master
    return None

# Your code here

Hint

Assign the function call result to current_master.

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