3 months ago
I'm seeing this error recently pop up in my Redis Deploy log. This is part of the n8n template with primary, postgres, redis and n8n-worker instances:
"synchronous AOF fsync is taking too long (disk is busy?). Writing the AOF buffer without waiting for fsync to complete, this may slow down Redis."
After some time it causes my n8n primary instance to fail and crash.
Any suggestions how I can improve the situation as it is getting to be impacting my day to day operations?
Thanks!
6 Replies
3 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
3 months ago
..
3 months ago
This appears to be an issue with the way your n8n is connecting to your database
Please go into the variables and change the:
QUEUE_BULL_REDIS_HOST from ${{Redis.REDISHOST}} to ${{Redis.REDISHOST_PRIVATE}}
QUEUE_BULL_REDIS_PORT from ${{Redis.REDISPORT}} to ${{Redis.REDISPORT_PRIVATE}}
For both the Worker and Primary
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Hi Jake - thanks for the quick response. I will update these settings later tonight when there is a good time to do so.
I did notice that since about the time you answered my post, I also stopped seeing any crashes etc. on my n8n instances (primary, worker and redis)... did you make any adjustments on your side?
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Thanks for letting me know - so far all is now working well without any problems. AI'll mark the ticket as resolved for now. Thanks for the quick support!
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Solved mskermit • 3 months ago