RedisCommandException: OOM command not allowed under OOM prevention
Basically, we're getting an OOM error to a get/set command, this can happen if the system runs out of memory. Even if cache-eviction is enabled, memory can be fragmented too much, or other bad thing.
Conclusion was that commands like get/set can fail, even when redis is just used as a cache. There is no really good way to handle it. It might be safest to simply close the connection and try again later.
We have seen cases with:
Basically, we're getting an
OOMerror to a get/set command, this can happen if the system runs out of memory. Even if cache-eviction is enabled, memory can be fragmented too much, or other bad thing.Conclusion was that commands like
get/setcan fail, even when redis is just used as a cache. There is no really good way to handle it. It might be safest to simply close the connection and try again later.