-
Notifications
You must be signed in to change notification settings - Fork 605
Description
I have recently had some issues with the redis container starting and then immediately terminating on my standalone instance running version 2.4.190. I'm unsure of the root cause, the redis logs show the instance starting and then immediately failing, see - redis-server.log
For quite some time I put this down to ElasticSearch memory utilisation leaving insufficient memory for redis and tried to adjust accordingly. This may have been part of the issue, also if the redis buffers had grown too large as redis has a memory limit of 812 MB. What I've ended up with is a corruption of the redis database.
I managed to resolve by deleting the database and restarting redis.
mv /nsm/redis/data/dump.rdb /nsm/redis/data/dump.rdb.corrupted.backup
so-redis-start
After a reboot, and limiting ElasticSearch to 8GB, memory seems to be back to normal levels:
$ free -h
total used free shared buff/cache available
Mem: 30Gi 9.7Gi 9.8Gi 18Mi 11Gi 21Gi
Swap: 8.0Gi 82Mi 7.9Gi
I'm wondering whether its possible for redis to be uplifted to the latest version to help prevent this issue as there have been some listpack fixes since 7.2.11. i.e. redis/redis#14357