Skip to content
Scaling replicas restarts all replicas
Anonymous
OP

3 months ago

When scaling replicas up or down, ALL replicas are restarted no matter what. This causes obvious issues where reconnects are happening unnecessarily.

Solved$20 Bounty

Pinned Solution

Changing service configurations require a full redeployment.

5 Replies

Railway
BOT

3 months ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • 3 months ago


Changing service configurations require a full redeployment.


0x5b62656e5d

Changing service configurations require a full redeployment.

Anonymous
OP

3 months ago

It seems like most service configurations should trigger full redeployment except replica sizing.


Is there a reason you would not want replicas to not restart?


0x5b62656e5d

Is there a reason you would not want replicas to not restart?

Anonymous
OP

3 months ago

Because current long running connections like websocket/tcp connections have to re-connect causing a thundering herd.


Anonymous
OP

3 months ago

brand new deployment id’s are assigned to replicas when scaling up or down. That’s how I know all replicas are being purged.


Status changed to Solved 0x5b62656e5d • about 13 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...