2 ms·
There's valid reasons to want the typical exit not to look like a catastrophic one even if that's a recoverable situation. That my application went down from s
by XorNot 2y ago
There's valid reasons to want the typical exit not to look like a catastrophic one even if that's a recoverable situation.
That my application went down from sig int makes a big difference compared to kill.
Blue-Green migrations for example require a graceful exit behavior.
- shoo 2y ago> Blue-Green migrations for example require a graceful exit behavior. it may not always be necessary. e.g. if you are deploying a new version of a stateless backend service, and there is a load balancer forwarding traffic to current version and new version backends, the load balancer could be responsible for cutting over, allowing in flight requests to be processed by the current version backends while only forwarding new requests to the new backends. then the old backends could be ungracefully terminated once the LB says they are not processing any requests.