[
https://issues.apache.org/jira/browse/MESOS-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15629426#comment-15629426
]
Gastón Kleiman commented on MESOS-6457:
---------------------------------------
I am afraid that {{TASK_LOST}} is not a terminal state. A slave rejoining the
cluster after a master failover might make tasks go from {{TASK_LOST}} to
{{TASK_RUNNING}}.
If I understand Neil correctly, tasks could do the {{TASK_KILLING => TASK_LOST
=> TASK_RUNNING}} transition only if an executor transitions them while the
slave is disconnected from the cluster.
> 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
> Affects Versions: 0.28.2, 1.0.1
> 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)
