Redis dropping connection and not restarting on multiple environments simultaneously
New to railway and hope someone can help.
I have a Nest Api deployed on two environments (develop and production) and each are connected to a Redis instance via the public URL (am having issues with PRIVATE_URL but will test the "sleep 3" fix shortly). Unfortunately, once a day, the connection to Redis drops and it does not reconnect leaving my API service completely unavailable. This happens at the exact same time on both environments which makes me believe it's related to Railway or connected to a deploy somehow (although each env is associated with a different branch / deployment cycle).
For context, this project is an NX monorepo. I saw another similar post but with no clear resolution and in my scenario, the APIs are getting hit regularly.
Has anyone experienced this? Any suggestions? PS: I will followup with the exact error when it happens again. I disabled redis on production env for now since it is not critical at the moment but will be soon. Thanks in advance.
Has anyone experienced this? Any suggestions? PS: I will followup with the exact error when it happens again. I disabled redis on production env for now since it is not critical at the moment but will be soon. Thanks in advance.
8 Replies
there's an ongoing incident that is likely related to this issue #🚨｜incidents
@Brody Thanks. I have experiencing this issue for about a week though. How long has this incident been active?
it was just today
you can sometimes get this error when you are arent closing connections
Ok, thanks. Any idea why it may not be restarting?
im sorry i dont know, but this would be a code issue
Thanks. How about the fact that it happens on multiple environments at the same time?
same code
Thanks