[
https://issues.apache.org/jira/browse/AURORA-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14491200#comment-14491200
]
Stephan Erb commented on AURORA-1275:
-------------------------------------
Mailing list discussion:
https://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201503.mbox/%[email protected]%3E
Review request: https://reviews.apache.org/r/32889/
> Don't delay kill sequence when HTTP teardown signal could not be dispatched
> ---------------------------------------------------------------------------
>
> Key: AURORA-1275
> URL: https://issues.apache.org/jira/browse/AURORA-1275
> Project: Aurora
> Issue Type: Story
> Components: Executor, Thermos
> Reporter: Stephan Erb
> Assignee: Stephan Erb
>
> 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.
> Advantages:
> * 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
