KeyDB Flash storage backend causing OOM erros reddit / selfhosted ---------------------------------------------------------------------- harshv8 · 2023-12-24 16:01 Hi, I have been trying to use keydb as a redis alternative because I wanted a simple DB with sets, lists and similar data structures without the hassle of tables etc. I followed their setup guides and the docs and setup the flash storage using docker but every time I try to write data more than the maxmemory value the client crashes with an OOM error and the server logs the same but is completely unresponsive after that. This should not be happening according to their youtube video that i had found. Any help is appreciated (even pointing me towards the correct forum if this is not it). ​ What i want is redis data structures without the huge memory requirements (which i thought keydb is supposed to do). How do i write GBs of data to this keydb instance but make sure that I do not use more than 500MB RAM for example .. I am fine with the lower speed and higher latency but it should not be OOM like this. ​ KeyDB version=6.3.4 Docker compose file: version: '3' services: keydb: image: eqalpha/keydb container_name: keydb volumes: - "./keydb.conf:/etc/keydb/keydb.conf:ro" - "flash:/flash" command: keydb-server /etc/keydb/keydb.conf network_mode: host volumes: flash: external: false keydb.conf file: server-threads 4 requirepass testpass storage-provider flash /flash maxmemory 40M maxmemory-policy allkeys-lfu save "" Docker Logs when the client sends 28th MB of data keydb | 1:485:M 24 Dec 2023 15:52:59.629 # Key cache exceeds maxmemory, freeing - performance may be affected increase maxmemory if possible Python client error message: ResponseError: OOM command not allowed when used memory > 'maxmemory'. ​ ---------------------------------------------------------------------- [deleted] · 2023-12-24 16:03 [deleted] ---------------------------------------------------------------------- daedric · 2023-12-24 17:15 Show please keydb.conf