[
https://issues.apache.org/jira/browse/AURORA-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976726#comment-14976726
]
Brian Weber commented on AURORA-279:
------------------------------------
Isn't that the standard action anyway? If the task is unhealthy beyond a
configured time, then thermos kills off the task, right?
The point of this is to have a service-level perspective, not just a task-level
perspective, so that the entire service doesn't get killed.
> 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)
