You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Abhishek Dasgupta (JIRA)" <ji...@apache.org> on 2016/02/03 11:22:39 UTC

[jira] [Commented] (MESOS-4547) Introduce TASK_KILLING state.

    [ https://issues.apache.org/jira/browse/MESOS-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130191#comment-15130191 ] 

Abhishek Dasgupta commented on MESOS-4547:
------------------------------------------

Hi Benjamin and Qian,
Currently I have bandwidth to work on this ticket. If Qian has no issue then I can start working on this ticket now. Have you, Qian?

> Introduce TASK_KILLING state.
> -----------------------------
>
>                 Key: MESOS-4547
>                 URL: https://issues.apache.org/jira/browse/MESOS-4547
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Benjamin Mahler
>              Labels: mesosphere
>
> Currently there is no state to express that a task is being killed, but is not yet killed (see MESOS-4140). In a similar way to how we have TASK_STARTING to indicate the task is starting but not yet running, a TASK_KILLING state would indicate the task is being killed but is not yet killed.
> This would need to be guarded by a framework capability to protect old frameworks that cannot understand the TASK_KILLING state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)