Difference between revisions of "OOM command not allowed when used memory ..."
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| 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. | ||
| Line 17: | Line 18: | ||
== See also == | == See also == | ||
| − | * {{redis-cli}} | + | * {{redis-cli memory}} |
* {{OOM}} | * {{OOM}} | ||
| − | |||
[[Category:Memory]] | [[Category:Memory]] | ||
| + | [[Category:Redis]] | ||
Latest revision as of 11:11, 4 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[edit]
maxmemory maxmemory-policy noeviction
See also[edit]
Advertising:
