You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gastón Kleiman (JIRA)" <ji...@apache.org> on 2016/11/01 17:22:58 UTC
[jira] [Commented] (MESOS-6457) Tasks shouldn't transition from
TASK_KILLING to TASK_RUNNING.
[ https://issues.apache.org/jira/browse/MESOS-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15626057#comment-15626057 ]
Gastón Kleiman commented on MESOS-6457:
---------------------------------------
[~zhitao] yes, this behaviour only affect the default and the command executors.
I believe that it is still possible for a task in {{TASK_KILLING}} to transition to {{TASK_LOST}}. Given that {{TASK_LOST}} is not a terminal state, I don't know if it would then be possible for the task to transition to {{TASK_RUNNING}} instead of to {{TASK_KILLING}}/{{TASK_KILLED}}. Maybe [~neilc] knows.
> Tasks shouldn't transition from TASK_KILLING to TASK_RUNNING.
> -------------------------------------------------------------
>
> Key: MESOS-6457
> URL: https://issues.apache.org/jira/browse/MESOS-6457
> Project: Mesos
> Issue Type: Bug
> Reporter: Gastón Kleiman
> Assignee: Gastón Kleiman
> Priority: Blocker
>
> A task can currently transition from {{TASK_KILLING}} to {{TASK_RUNNING}}, if for example it starts/stops passing a health check once it got into the {{TASK_KILLING}} state.
> I think that this behaviour is counterintuitive. It also makes the life of framework/tools developers harder, since they have to keep track of the complete task status history in order to know if a task is being killed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)