[
https://issues.apache.org/jira/browse/MESOS-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16368048#comment-16368048
]
Gastón Kleiman edited comment on MESOS-8530 at 3/23/18 2:18 AM:
----------------------------------------------------------------
https://reviews.apache.org/r/65692/
https://reviews.apache.org/r/65693/
https://reviews.apache.org/r/66232/
https://reviews.apache.org/r/65694/
https://reviews.apache.org/r/66233/
https://reviews.apache.org/r/65962/
https://reviews.apache.org/r/66234/
was (Author: gkleiman):
https://reviews.apache.org/r/65692/
https://reviews.apache.org/r/65693/
https://reviews.apache.org/r/65694/
https://reviews.apache.org/r/65695/
https://reviews.apache.org/r/66123/
> Default executor tasks can get stuck in KILLING state
> -----------------------------------------------------
>
> Key: MESOS-8530
> URL: https://issues.apache.org/jira/browse/MESOS-8530
> Project: Mesos
> Issue Type: Bug
> Components: executor
> Affects Versions: 1.2.3, 1.3.1, 1.4.1, 1.5.0
> Reporter: Gastón Kleiman
> Assignee: Gastón Kleiman
> Priority: Critical
> Labels: default-executor, mesosphere
>
> The default executor will transition a task to {{TASK_KILLING}} and mark its
> container as being killed before issuing the {{KILL_NESTED_CONTAINER}} call.
> If the kill call fails, the task will get stuck in {{TASK_KILLING}}, and the
> executor won't allow retrying the kill.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
