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 2017/06/14 00:19:00 UTC
[jira] [Created] (MESOS-7662) Documentation regarding TASK_LOST is
misleading
Gastón Kleiman created MESOS-7662:
-------------------------------------
Summary: Documentation regarding TASK_LOST is misleading
Key: MESOS-7662
URL: https://issues.apache.org/jira/browse/MESOS-7662
Project: Mesos
Issue Type: Bug
Components: documentation
Reporter: Gastón Kleiman
Assignee: Gastón Kleiman
Our protos describe {{TASK_LOST}} as a terminal state [\[1\]|https://github.com/apache/mesos/blob/fb54d469dcadf762e9c3f8a2fed78ed7b306120a/include/mesos/mesos.proto#L1722] [\[2\]|https://github.com/apache/mesos/blob/fb54d469dcadf762e9c3f8a2fed78ed7b306120a/include/mesos/mesos.proto#L64-L73].
A task might go from {{TASK_LOST}} to {{TASK_RUNNING}} or another state if Mesos is not using a strict register, so the documentation is misleading.
Marathon used to assume that {{TASK_LOST}} was a terminal past and that resulted in production pain for some users.
We should update the documentation to make the life of frameworks developers a bit better =).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)