Redis Cloud OOM command not allowed when used memory > maxmemory

How to fix it

// try these in order, the most common fix is first

1. FIX 1Find what uses memory

   Copy steps
   1. 01Open Redis Insight and run Memory Analyzer
   2. 02Run redis-cli --bigkeys
   3. 03Delete or expire the largest unneeded keys
   Did this fix it? Yes No

2. FIX 2Change eviction policy

   Copy steps
   1. 01Database > Configuration > Data eviction policy
   2. 02Choose allkeys-lru for a cache, or volatile-lru if only TTL keys may go
   3. 03Save
   Did this fix it? Yes No

3. FIX 3Raise the memory limit

   Copy steps
   1. 01Upgrade the plan or memory size in Configuration
   2. 02Expect the monthly price to rise with size
   Did this fix it? Yes No

Symptoms

Writes fail with 'OOM command not allowed when used memory > maxmemory'.

Why it happens

• C-01Free 30 MB or Essentials limit reached
• C-02Keys without TTL accumulating
• C-03Policy is noeviction
• C-04Large keys/streams

// this guide also covers

• redis oom command not allowed
• redis cloud out of memory
• redis cloud maxmemory

Other Redis Cloud errors

• Redis Cloud Connection Timeout
• Redis Cloud Connection Refused
• Redis Cloud WRONGPASS / NOAUTH Authentication Error
• Redis Cloud SSL / TLS Connection Error
• Redis Cloud ERR max number of clients reached
• Why Is Redis Cloud Slow / High Latency
• Redis Cloud Cannot Connect From My IP (Allowlist / Source IP)
• Redis Cloud Data Lost / Keys Disappeared