2 years ago
With a memory leak, I need to restart my service every once in a while but I hesitate to use a cron job because unlike deployments, my 2 replicas are restarted at the same time. This causes downtime for about 20 seconds.
Any workarounds here?
My service is on V2 runtime.
5 Replies
2 years ago
We've moved your service domain to the new edge proxy, which allows for zero downtime deploys.
Rolling restarts shouldn't be needed going forward.
If you do need to restart the service periodically you may try using this template: https://railway.app/template/fwH-l3
Otherwise we're currently working to improve crons generally and will incorporate your feedback into our roadmap
Thanks!
Status changed to Awaiting User Response Railway • over 1 year ago
2 years ago
Was it not on the edge proxy a few hours ago? I noticed that toggle went away on my service so I assumed it was already there and the legacy proxy had been disabled.
Status changed to Awaiting Railway Response Railway • over 1 year ago
2 years ago
Fair assumption but it was previously on the legacy proxy. Sorry for the rough edges here. Thanks
Status changed to Awaiting User Response Railway • over 1 year ago
2 years ago
Thanks for confirming! Makes me feel more confident for when I try again :)
Status changed to Awaiting Railway Response Railway • over 1 year ago
2 years ago
All good! Feel free to raise up anything else if you run into it :)
Status changed to Awaiting User Response Railway • over 1 year ago
7 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 7 months ago