Vinod Kone created MESOS-217:
--------------------------------
Summary: LOST tasks are incorrectly reconciled between mesos and
framework
Key: MESOS-217
URL: https://issues.apache.org/jira/browse/MESOS-217
Project: Mesos
Issue Type: Bug
Reporter: Vinod Kone
When a slave is removed from the master (e.g. due to a broken libprocess), the
task is considered LOST by the master. It then sends an update to the framework.
When the slave successfully re-registers, it informs the master that the task
is RUNNING (which it is). Now, the master and slave think the task is in
RUNNING, but the framework thinks its LOST.
This is related to MESOS-205.
I believe this issue will be fixed, when the slave doesn't remove a slave for
libprocess disconnections.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira