Difference between revisions of "OOM command not allowed when used memory ..."
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
* [[Redis memory footprint]] | * [[Redis memory footprint]] | ||
* <code>[[redis-cli info memory]]</code> | * <code>[[redis-cli info memory]]</code> | ||
| + | |||
| + | maxmemory | ||
| + | maxmemory-policy noeviction | ||
== See also == | == See also == | ||
Revision as of 10:22, 30 September 2022
OOM command not allowed when used memory > ‘maxmemory’
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 - 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:
