[
https://issues.apache.org/jira/browse/AURORA-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976706#comment-14976706
]
Stephan Erb commented on AURORA-279:
------------------------------------
Another way would be to do this somewhat inverse: The executor signals the
framework that the task is unhealthy. It is then up to the framework to kill
the offending executor.
Mesos has first-class support to implement this health notification [1].
[1]
https://github.com/apache/mesos/blob/3c35a6b20dc07228ca30ad2d00115017224284a1/include/mesos/mesos.proto#L1155
> Allow scheduler to decide how to respond to task health check failures
> ----------------------------------------------------------------------
>
> Key: AURORA-279
> URL: https://issues.apache.org/jira/browse/AURORA-279
> Project: Aurora
> Issue Type: Story
> Components: Executor, Scheduler
> Reporter: Bill Farner
> Priority: Minor
>
> The executor is currently autonomous in deciding to kill tasks that have
> failed health checks. If health check failures synchronize across a service,
> the service could suffer an outage. SLA considerations may also need to be
> me made before deciding to kill a task for health check failures.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
