You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2013/09/06 20:59:51 UTC
[jira] [Created] (MESOS-681) Document known cases where updates can
be lost.
Benjamin Mahler created MESOS-681:
-------------------------------------
Summary: Document known cases where updates can be lost.
Key: MESOS-681
URL: https://issues.apache.org/jira/browse/MESOS-681
Project: Mesos
Issue Type: Task
Reporter: Benjamin Mahler
Fix For: 0.15.0
Once we have a Registrar in the master persistently storing slave information, there will remain a smaller number of scenarios where updates can be lost in the system. This ticket is to carefully think through and document these cases so that we can identify possible improvements.
For example, if a slave machine fails and is not brought back up, and the master fails over during this time. Then the master will send a slaveLost signal to the scheduler (but will not be able to send TASK_LOST for each individual task that was on the slave).
This way, framework developers will get a better sense of how reliable status updates are, and under what circumstances they may not be delivered.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira