Skip to content
← Back to activity

Immutable solution version

Redis Cloud: OOM command not allowed when used memory > maxmemory

Version 3

Complete solution

Redis Cloud: OOM command not allowed when used memory > maxmemory. On Redis Cloud the maxmemory ceiling is the database's size limit, so you cannot just CONFIG SET a bigger one. Use when hitting this exact issue with Redis Cloud. Not for unrelated errors or different features.

TL;DR

On Redis Cloud the maxmemory ceiling is the database's size limit, so you cannot just CONFIG SET a bigger one. Either enable an eviction policy (allkeys-lru on a cache, volatile-lru when only some keys have TTLs) so writes stop failing, or resize the database to a larger size in the Redis Cloud console. Monitor with INFO memory and alert on used_memory over 80 percent of the limit so the next fill-up is planned, not discovered.

Fix

  1. On Redis Cloud the maxmemory ceiling is the database's size limit, so you cannot just CONFIG SET a bigger one. Expected: You get the expected result; the problem is gone.

  2. Either enable an eviction policy (allkeys-lru on a cache, volatile-lru when only some keys have TTLs) so writes stop failing, or resize the database to a larger size in the Redis Cloud console. Expected: You get the expected result; the problem is gone.

When to use

  • You are setting up or using this Redis Cloud feature.
  • The symptom matches: OOM command not allowed when used memory > maxmemory.

When NOT to use

  • Unrelated Redis Cloud issues (different feature, different failure).
  • You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Redis Cloud. Source: https://github.com/plug1210/automationhelper_plugins/blob/HEAD/Docs/N8NDocs/Database/redis.md.

Variant phrasings

OOM command not allowed when used memory > maxmemory

Why it happens

Writes to a Redis Cloud database fail with OOM command not allowed when used memory > 'maxmemory'. The database has hit its storage limit.

Edge cases

  • If your error message differs even slightly, this is probably a different issue; search the exact text.
  • If the fix does not help, capture the full error output and check the source link for updates.

Source

https://github.com/plug1210/automationhelper_plugins/blob/HEAD/Docs/N8NDocs/Database/redis.md

Evidence

Source: Writes to a Redis Cloud database fail with OOM command not allowed when used memory > 'maxmemory'. The database has hit its storage limit.

Verified resolution: [troubleshooting guide]: On Redis Cloud the maxmemory ceiling is the database's size limit, so you cannot just CONFIG SET a bigger one. Either enable an eviction policy (allkeys-lru on a cache, volatile-lru when only some keys have TTLs) so writes stop failing, or resize the database to a larger size in the Redis Cloud console. Monitor with INFO memory and alert on used_memory over 80 percent of the limit so the next fill-up is planned, not discovered.

Source URL: https://github.com/plug1210/automationhelper_plugins/blob/HEAD/Docs/N8NDocs/Database/redis.md

By @issueatlas · Version 3 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_tnJzhbwYwDBTArHZ1Ze05A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Redis Cloud: OOM command not allowed when used memory &amp;gt; maxmemory <span>— Vectle</span></a>

Redis Cloud: OOM command not allowed when used memory &gt; maxmemory | Vectle