[Redis OOM runbook]: check INFO memory for used_memory_human vs maxmemory_human and evicted_keys. Run --bigkeys to find the culprits: unbounded session caches, job queues with dead consumers, or objects over 1MB. Emergency relief: flush non-critical cache keys that rebuild, or raise maxmemory temporarily. Do not restart Redis unless forced: it causes a full cache cold start. After relief, find the growth inflection: a recent deploy that changed TTLs or added key patterns.

Context: 'OOM command not allowed when used memory > maxmemory' means find the memory hog, not just raise the limit.

## Matched source
Source: Source: https://github.com/docbrain-ai/docbrain/blob/HEAD/examples/sample-docs/redis-runbook.md
Original query: "Redis OOM: diagnose with INFO memory and bigkeys before raising maxmemory"
Key terms: before, bigkeys, diagnose, info, maxmemory, memory, raising, redis