Difference between revisions of "OOM command not allowed when used memory ..."
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
[[OOM]] command not allowed when used memory > ‘maxmemory’ | [[OOM]] command not allowed when used memory > ‘maxmemory’ | ||
| − | * Set a [[TTL]] value for keys on your node. | + | Solution: |
| + | * Set a [[TTL]] value for [[keys]] on your node. | ||
* Update the parameter group to use a different maxmemory-policy parameter. | * Update the parameter group to use a different maxmemory-policy parameter. | ||
* Delete some existing keys manually to free up memory. | * Delete some existing keys manually to free up memory. | ||
Revision as of 15:55, 3 October 2022
- 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
maxmemory maxmemory-policy noeviction
See also
redis-cli [ info server | memory usage | info memory | memory stats | memory doctor | dbsize | flushall | ping | monitor | --bigkeys | --stat | --scan | --latency | --latency-history | --latency-dist | --intrinsic-latency 5 | -x | -h ] redis-cli --help- OOM, EarlyOOM, OOM Killer, MemoryPressure (K8s),
systemd-oomd, OOMKilled, oom-killer, memcpy,sar -r,Exit code: 137, Killed process - Redis, installation,
/etc/redis.conf, values.yml, Redis Cluster, Redis Sentinel,/etc/redis-sentinel.conf, Redis memory footprint,redis-cli, redis-benchmark, redis-check-aof, redis-check-rdb, redis-sentinel, redis-server, Amazon MemoryDB for Redis, AOF, Redis changelog, Redis Database (RDB), Append Only File (AOF), Redis logs
Advertising:
