a year ago
Everytime we deploy we get somewhere between 30s-1m of downtime. Seems like a lot, how can we reduce this? We've upgraded to the v2 runtime, which deploys faster, but we still have a similar problem with downtime.
3 Replies
a year ago
Hello,
You have a volume so zero downtime deploys are not possible at this time because two deployments can't use the same volume at the same time, and that is where the downtime comes from, since we have to fully stop the old deploy before starting the new deploy.
Perhaps you could use MinIO as a storage solution instead of volumes, that way you can achieve true zero downtime deploys!
Best,
Brody
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
makes sense! thanks for the info.
Just FYI- when i removed the volume, it took down my app and started a completely fresh deploy instead of allowing the existing deploy (w/volume) to remain up until the new build was deployed. Probably worth giving an FYI in the product to let people know that they may
experience downtime.
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
That's intended, a redeploy is needed to remove the volume from the deployment as Podman does not support hot swapping volume mounts as far as I'm aware.
But power users can use alt + shift + enter to save an action and prevent a redeploy as long as you know you are about to make a deployment through GitHub.
Status changed to Awaiting User Response Railway • about 1 year ago
Status changed to Solved brody • about 1 year ago