Redis: OOM command not allowed when used memory > ‘maxmemory’

$ tail -f error.log
OOM command not allowed when used memory > ‘maxmemory’
This can happen every time a WRITE operations is sent to Redis, to store new data.

What does it mean?

The OOM command not allowed when used memory > ‘maxmemory’ error means that Redis was configured with a memory limit and that particular limit was reached. In other words: its memory is full, it can’t store any new data.

You can see the memory values by using the redis CLI tool.

$ redis-cli -p 6903

127.0.0.1:6903> info memory

Memory

used_memory:3221293632
used_memory_human:3.00G
used_memory_rss:3244535808
used_memory_peak:3222595224
If you run a Redis instance with a password on it, change the redis-cli command to this:

$ redis-cli -p 6903 -a your_secret_pass
The info memory command remains the same.

The example above shows a Redis instance configured to run with a ma