DoraPulse
All errors
REDIS-OOMCache

Redis OOM Command Not Allowed

Redis rejects writes with OOM command not allowed when used memory has exceeded maxmemory.

Root Cause & Remediation

Unbounded key growth, missing TTLs, a noeviction policy, or a hot key from a runaway producer.

Remediation steps

  1. 1Identify large keys with redis-cli --bigkeys or MEMORY USAGE.
  2. 2Apply TTLs to ephemeral keys and verify maxmemory-policy is appropriate (allkeys-lru for caches).
  3. 3Scale the node vertically or shard with Redis Cluster.
  4. 4Add producer-side rate limiting on the offending pattern.
  5. 5Enable persistence-aware eviction monitoring in the alerting stack.

DORA Risk Matrix

Typical classification
Context-dependent
Likelihood
Medium
Blast radius
Affects sessions, rate limiters and queues backed by Redis.
CIF impact
Login storms, idempotency loss and webhook backlog.
Analyst notes
Frequently MAJOR when Redis backs session auth for online banking or trading.

Ready to classify this incident?

Use the DoraPulse Triage Calculator to instantly determine if this event breaches DORA materiality thresholds and generate a ready-to-file regulatory draft for your internal compliance team.

Open Triage Calculator — Pre-filled for Redis OOM Command Not Allowed