Ilya Pronin created MESOS-8165:
----------------------------------
Summary: TASK_UNKNOWN status is ambiguous
Key: MESOS-8165
URL: https://issues.apache.org/jira/browse/MESOS-8165
Project: Mesos
Issue Type: Bug
Affects Versions: 1.4.0
Reporter: Ilya Pronin
Assignee: Ilya Pronin
Priority: Major
There's an ambiguousness in the definition of {{TASK_UNKNOWN}} status.
Currently it is sent by the master during explicit reconciliation when it
doesn't know about the task. This covers 2 situations that should be handled
differently by frameworks:
# Task is unknown, agent is unknown - we don't know the fate of the task, it's
reasonable for the framework to wait until the task comes back (if SLA allows);
# Task is unknown, agent is registered - task is definitely in the terminal
state and won't come back, the framework should reschedule it.
The second situation should produce {{TASK_GONE}} status.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
