Getting OOM with allkeys-lru, Redis version 3.2.0

[pala...@gmail.com]

I get in the logs:
Uncaught CredisException: OOM command not allowed when used memory > 'maxmemory'


even thought my configuration is:
maxmemory 16384mb
maxmemory-policy allkeys-lru

My understanding is that with allkeys-lru one would never get OOM conditions. Is it a bug?

[Itamar Haber]

Hello Palavets,

A bug is possible, but not mandatory. If possible, please provide more information:

* `INFO memory`

* `CONFiG GET maxmemory*`

* Info about the Credis command you're running

This may or may not be a related thread/topic: https://www.reddit.com/r/redis/comments/68fvpv/oom_get_in_hget/

Cheers,

Itamar

--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+unsubscribe@googlegroups.com.
To post to this group, send email to redi...@googlegroups.com.
Visit this group at https://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.

[pala...@gmail.com]

This happened a few times. At the time  maxmemory ( from config get and config file) was 4G
 and used_memory_peak_human was 4.14G. Also maxmemory-policy was and still is allkeys-lru.
After increasing maxmemory to 16G  it's fine because the used_memory is below 4G.

Same thing 100% as in the link you posted.
In the comments there is a suggestion it could be a client error but it seems like an error received from the server.