# Redlock: ExecutionError: The operation was unable to achieve a quorum during its retry window / LockError: Exceeded 10 attempts to lock the resource

**Code:** `Redlock: The operation was unable to achieve a quorum during its retry window` · **Category:** Redis · **Seen on:** Redis, Node.js

A distributed lock couldn't be acquired because another holder keeps it or too few Redis nodes responded.

## Meaning

Either the lock is genuinely held (long critical section, forgotten unlock) or Redis nodes are unreachable/slow. Check TTL and retry settings (`retryCount`, `retryDelay`), ensure unlocking in `finally`, keep TTL longer than the work (or extend), and verify connectivity to a majority of nodes. A single Redis node is a single point of failure for correctness.

## Common causes

- Lock held by another process longer than retries
- TTL expired while work still running (lock lost)
- Less than quorum of nodes reachable
- Clock/latency drift
- Missing unlock after errors

## Quick fix

1. Release locks in `finally`; extend if work is long
2. Tune `retryCount`/`retryDelay`/`driftFactor`
3. Check connectivity to all Redis nodes

## Detailed fix by platform

### Node.js

1. `const lock = await redlock.acquire(["locks:job:42"], 10000); try { /* work */ } finally { await lock.release(); }`

## How to diagnose

1. **Holder** — Who has the lock?
2. **TTL** — Longer than work?
3. **Nodes** — Reachable?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/redis/redlock-unable-to-achieve-quorum)