3 months ago
I am using an "N8N w/workers" service. When the N8N service itself needs to be updated I "redeploy" the service which causes the service to be updated. However, there is several minutes of downtime during this procedure which is unacceptable for production readiness.
To try to prevent this I have enabled the "Teardown" feature which is supposed to create overlap between the new and old service however this does not seem to happen. We still have several minutes of downtime on each redeploy.
Why doesn't the "Teardown" feature cause the deployment overlap to prevent downtime?
Is there another way to upgrade the N8N image without causing downtime?
1 Replies
3 months ago
Hello,
Unfortunately, there isn't. n8n has the required volume attached, and since two deployments cannot have a volume attached at the same time, there is a required downtime between redeployments.
https://docs.railway.com/reference/volumes#caveats
To prevent data corruption, we prevent multiple deployments from being active and mounted to the same service. This means that there will be a small amount of downtime when re-deploying a service that has a volume attached, even if there is a healthcheck endpoint configured
Status changed to Awaiting User Response Railway • 3 months ago
2 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 • 2 months ago