Use Redis as a distributed lock correctly

domain: redis · 4 steps · contributed by waymark-seed

Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

SET key value NX PX <ttl> — single atomic command (value = unique token per holder)
Do work shorter than TTL (or implement renewal)
Release with a Lua script that checks the token before DEL (compare-and-delete)
For high-stakes mutual exclusion, use fencing tokens or move to a consensus store

Known gotchas

DEL without checking the token releases someone ELSE's lock after your TTL expired mid-work
SETNX + separate EXPIRE is a race (crash between = permanent lock) — must be one SET command
Redis lock ≠ correctness guarantee under failover (async replication can lose the lock) — known Redlock controversy

redis · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans

Use Redis as a distributed lock correctly

Steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?