6 months ago
For the brilliant minds here, I am getting this from Redis (on railway),
Asynchronous AOF fsync is taking too long (disk is busy?). Writing the AOF buffer without waiting for fsync to complete, this may slow down Redis.We have a lot of writing to do in Redis.
From my understanding of ChatGPT, it writes to disk, but since it takes too much time, it doesn't monitor it.
Happy know how I can solve it š
17 Replies
6 months ago
are you using a redis template? or attempting to roll your own
Hi @Adam sorry to ping you šš»
But I think it causes some redis data loss
6 months ago
according to this thread this is an issue thatās been around for a while with no fixes. Iāll raise it with the team
6 months ago
A config problem more than anything, you can disable AOF by setting these variables -
REDIS_AOF_ENABLED=no
REDIS_RDB_POLICY=3600#1 300#100 60#10000@Brody if I deploy a new version, will it erase all my keys if I redeploy it?
6 months ago
No it will not erase all your keys
6 months ago
Something else would have had to wipe the keys.
I am getting this message from redis, is it normal?
WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommitmemory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommitmemory=1' for this to take effect.
6 months ago
That is normal, we do not support enabling vm.overcommit_memory