Redis Caching & Messaging (Pub/Sub, Streams) · Leçon

Verrous distribués avec Redis

Mettez en œuvre des mécanismes fiables de verrouillage distribué avec Redis pour coordonner les accès dans les systèmes concurrents.

Verrous distribués avec Redis est une leçon Redis Caching & Messaging (Pub/Sub, Streams) gratuite sur CoddyKit. Ceci est la leçon 1 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage Redis Caching & Messaging (Pub/Sub, Streams), et ta progression se synchronise sur le web et l'application CoddyKit. Le cours Redis Caching & Messaging (Pub/Sub, Streams) comprend 4 leçons au total.

Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.

The Need for Distributed Locks

Imagine multiple applications or services trying to update the same piece of data, like a user's balance or a unique order ID. Without coordination, they could overwrite each other's changes, leading to data corruption or incorrect states.

Race conditions: When operations depend on specific timing, leading to unpredictable results.
Data integrity: Ensuring shared resources remain consistent.
Concurrency control: Managing access when multiple processes run simultaneously.

Distributed locks are like a single key to a shared room. Only one process can hold the key (lock) at a time, ensuring exclusive access.

Why Redis for Distributed Locks?

Redis is an excellent choice for implementing distributed locks due to its speed, atomic operations, and single-threaded nature.

Atomicity: Redis commands are executed atomically, meaning they complete entirely or not at all, preventing partial updates.
Performance: In-memory operations ensure very low latency for lock acquisition and release.
Simplicity: Basic string commands can be leveraged effectively for locking.

These features allow Redis to manage lock states reliably and efficiently across many different application instances.

Basic Lock Acquisition (SET NX EX)

The core of a Redis-based lock lies in the SET command with specific options:

NX (Not eXists): Ensures the key is only set if it doesn't already exist. This is how we acquire the lock exclusively.
EX (EXpire): Sets an expiration time for the key in seconds. This is crucial to prevent deadlocks if a client crashes before releasing the lock.
value: A unique identifier for the lock holder (e.g., a UUID). This allows only the original lock holder to release it.

The command looks like this: SET mylock:resource <unique_id> NX EX 30

Acquiring a Lock: Code Example

Here's a simplified example of how a client might attempt to acquire a lock using Python. The SET command returns True (or 'OK') if the lock was acquired, and False (or None) otherwise.

import redis
import uuid

# Connect to Redis
r = redis.Redis(decode_responses=True)

lock_key = "resource:123:lock"
client_id = str(uuid.uuid4())
lock_timeout_seconds = 10

print(f"Client {client_id} attempting to acquire lock...")

# Attempt to acquire the lock
# set(name, value, nx=True, ex=timeout) maps to SET key value NX EX timeout
lock_acquired = r.set(lock_key, client_id, nx=True, ex=lock_timeout_seconds)

if lock_acquired:
  print(f"Client {client_id} acquired the lock!")
  # Simulate work
  # time.sleep(5)
  # ... do critical section work ...
  # r.delete(lock_key) # DON'T do this directly!
else:
  print(f"Client {client_id} failed to acquire the lock. It's held by someone else.")

# In a real app, you'd release the lock safely later.

The Challenge of Releasing a Lock Safely

Simply deleting the lock key (e.g., DEL mylock:resource) is NOT safe. Consider this scenario:

Client A acquires the lock with an expiration of 10 seconds.
Client A's operation takes longer than 10 seconds, so the lock expires automatically.
Client B acquires the lock for the same resource.
Client A's operation finally finishes and attempts to delete the lock. It unknowingly deletes Client B's lock!

This leads to two clients thinking they have the lock simultaneously, defeating its purpose. We need an atomic way to check ownership AND delete.

Atomic Release with Lua Scripts

Redis allows executing Lua scripts atomically. This means the entire script runs as a single, uninterruptible operation on the Redis server, solving our lock release problem.

The Lua script for releasing a lock typically does two things:

It checks if the current lock value matches the unique ID provided by the client attempting to release the lock.
If they match, it deletes the lock key.

This guarantees that only the client who originally acquired the lock (and whose unique ID is still stored) can release it, even if the lock has expired and been re-acquired by another client.

Releasing a Lock: Code Example

Here's how you'd execute a Lua script to safely release a lock. The script ensures that you only delete the lock if you are its rightful owner.

import redis
import uuid

r = redis.Redis(decode_responses=True)

lock_key = "resource:123:lock"
client_id = str(uuid.uuid4())
lock_timeout_seconds = 10

# Assume client_id has previously acquired the lock
# For demonstration, let's manually set it:
r.set(lock_key, client_id, nx=True, ex=lock_timeout_seconds)
print(f"Client {client_id} acquired the lock for demo.")

lua_script = """
  if redis.call('GET', KEYS[1]) == ARGV[1] then
    return redis.call('DEL', KEYS[1])
  else
    return 0
  end
"""

# Execute the Lua script
# KEYS[1] is lock_key, ARGV[1] is client_id
released = r.eval(lua_script, 1, lock_key, client_id)

if released:
  print(f"Client {client_id} successfully released the lock.")
else:
  print(f"Client {client_id} failed to release the lock (not owner or already expired).")

# Check if the key still exists
if r.exists(lock_key):
  print(f"Lock key '{lock_key}' still exists.")
else:
  print(f"Lock key '{lock_key}' does not exist.")

Lock Expiration & Renewal

The EX (expiration) option is vital. It acts as a safety net, ensuring locks are eventually released even if the client crashes or fails to release it. Without expiration, a crashed client could hold a lock indefinitely, causing a permanent deadlock.

Too short: If the expiration is too short, long-running tasks might lose their lock prematurely.
Too long: If it's too long, deadlocks might persist for an unacceptable duration.

For tasks that might exceed the initial expiration, clients can implement a 'lock renewal' mechanism. This involves periodically checking if they still hold the lock and, if so, extending its expiration time using EXPIRE or PEXPIRE commands.

Redlock: For Higher Guarantees

While a single Redis instance with SET NX EX works for many cases, it has a single point of failure. If that Redis instance goes down, all locks are lost or become unavailable.

The Redlock algorithm addresses this by requiring clients to acquire locks on a majority of independent Redis master instances (e.g., 3 out of 5). This provides higher guarantees:

Fault tolerance: If one Redis instance fails, the system can still function.
Stronger safety: Reduces the chance of multiple clients acquiring the same lock.

Redlock is more complex to implement but offers a robust solution for critical distributed systems.

Quick Check: Lock Properties

Which of the following are essential properties for a reliable distributed lock using Redis, assuming a single Redis instance?

Recap: Distributed Locks with Redis

In this lesson, we explored how to implement reliable distributed locks using Redis.

We learned that SET key value NX EX seconds is the foundation for acquiring a lock atomically.
A unique value identifies the lock holder, preventing others from releasing it.
Expiration (EX) is vital for preventing permanent deadlocks if a client crashes.
Safely releasing a lock requires an atomic check-and-delete operation, typically achieved with Lua scripting.
For higher reliability and fault tolerance in multi-instance setups, the Redlock algorithm can be employed.

Understanding these principles is key to building robust and concurrent distributed applications.

Questions Fréquemment Posées

La leçon « Verrous distribués avec Redis » est-elle gratuite ?

Oui — le texte complet de « Verrous distribués avec Redis » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours Redis Caching & Messaging (Pub/Sub, Streams), passe à CoddyKit PRO. Le cours Redis Caching & Messaging (Pub/Sub, Streams) comprend 4 leçons au total.

Qu'est-ce que j'apprendrai dans « Verrous distribués avec Redis » ?

Mettez en œuvre des mécanismes fiables de verrouillage distribué avec Redis pour coordonner les accès dans les systèmes concurrents. Tu pratiques Redis Caching & Messaging (Pub/Sub, Streams) avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.

Dois-je avoir de l'expérience pour commencer Redis Caching & Messaging (Pub/Sub, Streams) ?

Aucune expérience préalable n'est requise. Redis Caching & Messaging (Pub/Sub, Streams) sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 1 sur 4.

Combien de temps prend la leçon « Verrous distribués avec Redis » ?

La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.

Peux-tu écrire et exécuter du code dans cette leçon Redis Caching & Messaging (Pub/Sub, Streams) ?

Oui. Chaque leçon Redis Caching & Messaging (Pub/Sub, Streams) inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.

Toutes les leçons de ce cours

← Retour à Redis Caching & Messaging (Pub/Sub, Streams)