The Thermos task runner performs a kill escalation sequence by dispatching calls to the HTTP endpoints /quitquitquit and /abortabortabort before stopping a task for good. After each of these calls it waits for 5 seconds.
The runner should not perform the waiting when the corresponding shutdown request could not be dispatched.
- Services which use a health port but don't implement /qqq and /aaa are not taxed by a total of 10 seconds waiting time for each kill operation
- The whole system is faster to react when services are meant to be restarted due to failing health checks. Failing health checks often imply an application is not responding at all, including the endpoints /qqq and /aaa