few hours

n/a

Thank you. 1hr is well more than enough.

I assume this will not change any time soon? (If so, a warning would be great)

I don't see why we would change it, a lot of customers use it

Fantastic. Thanks for the info.

One small feedback: this config was hard to find btw, b/c I was looking all over "deployments" and "zero downtime" but finally found it here: https://docs.railway.com/reference/variables

did you use the search bar?

I did. but my search terms (i think mainly "deployment" etc) weren't hitting that, at least i didn't notice

where else in the docs do you think it would be applicable to mention it?

Hmm. Definitely I was hoping for "zero downtime" hits.

e.g.

https://docs.railway.com/guides/healthchecks-and-restarts#configure-healthcheck-path

https://docs.railway.com/reference/healthchecks

I don't think the variable has much to do with zero downtime though?

your new service would have already come online regardless of that variable

A bit subtle I suppose.

For the semantics of my project, SIGTERMing a running container, even if there are no unresponded HTTP requests, or no open TCP sockets, means downtime. The long job could be cut in half.

I agree it's not exactly related

I'm just realizing I've mentioned the wrong variable here -

your new service would have already come online regardless of that variable

while this is true, in my case the new deployment would be completely unaware of the active job. (Note: it could be designed to, but that's a bit overkill in my case)

RAILWAY_DEPLOYMENT_DRAINING_SECONDS is not the one you mentioned?

it says overlap when it should be draining

I'm sorry, I'm confused.

Such as in this thread: https://discord.com/channels/713503345364697088/1290350655222841345/1290354036062818397

I see I can arbitrarily extend the life of the old deployment with RAILWAY_DEPLOYMENT_OVERLAP_SECONDS

but all I need (which I believe is exclusive in behavior to that one) is for the new deploy to come up as normal, but the old deploy to (possibly) hang on SIGTERM for a few minutes, to be decided by the old deploy app at runtime.

So i'd like to know the max time for both, I suppose

you want draining, the variable you asked about originally

I don't have an exact time, so I'm safely saying a few hours

Ok, great.

!s