[
https://issues.apache.org/jira/browse/MESOS-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124596#comment-15124596
]
Qian Zhang commented on MESOS-4547:
-----------------------------------
Thanks [~bmahler] for the clarification. And besides introducing a new
TaskState ({{TASK_KILLING}}), we will also introduce a new framework capability
in FrameworkInfo.Capability (currently we only have {{REVOCABLE_RESOURCES}}),
and Mesos will only send {{TASK_KILLING}} to the framework which enables this
capability, right?
I am indeed interested in this ticket, but I am currently working on other
tickets, so I'd like to know if this is a urgent one (e.g., which release do we
want it merged in?), if it is not that urgent, I'd like to work on it :-)
> 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)
