Railway running two copies of my container during health checks
I am running into an edge case in my project where two copies of my container are running during health checks. This is causing weird issues, is there a way to turn this off or mitigate this?
17 Replies
Project ID:
N/A
N/A
are you using replicas
This demonstrates the problem. I push a new commit and it deploys a new copy of my container + runs health check. 1-2min later, it will shutdown the original and keep the new one up
This is a discord bot, so I end up with doubled replies when both are running.
youre not nathan
There are two of us
Haha
explain 🤣
We are working on the same project together. I just wanted to kick off the thread.
gotcha
set
RAILWAY_DEPLOYMENT_OVERLAP_SECONDS
to 0
This is an environment variable?
service variable, yeah
Fancy, will give that a shot. Thanks!
🎉
desired effect accomplished?
That seemed to fix it. Thank you!
no problem!