OOM command not allowed when used memory ...

• https://redis.io/docs/getting-started/faq/#whats-the-redis-memory-footprint
• https://aws.amazon.com/premiumsupport/knowledge-center/oom-command-not-allowed-redis/

OOM command not allowed when used memory > ‘maxmemory’

Solution:

• Set a TTL value for keys on your node.
• Update the parameter group to use a different maxmemory-policy parameter.
• Delete some existing keys manually to free up memory.
• Choose a larger node type.

Related

• Redis memory footprint
• redis-cli info memory

maxmemory
maxmemory-policy noeviction

See also

• Redis memory footprint: redis-cli info memory, redis-cli memory stats, redis-cli memory doctor, redis-cli memory usage
• OOM, EarlyOOM, OOM Killer, MemoryPressure (K8s), systemd-oomd, OOMKilled, oom-killer, memcpy, sar -r, Exit code: 137, Killed process