Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Stop gracefully on SIGTERM #21
When an instance fails the healthcheck, paasta sends a SIGTERM, waits a bit and then kills the process if it hasn't stopped yet.
Right now we don't catch SIGTERM, so the process dies as soon as it receives it. All in-flight requests are lost and clients see this as a 503.
So far I haven't able to solve this problem, but here's a repro:
The request to
Connection is aborted and we get "curl: (52) Empty reply from server", docker shuts down at the same time
Some things that might be useful to note here