You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2013/08/02 07:27:49 UTC
[jira] [Commented] (MESOS-611) Refactor slave recovery to ensure
slave recovers its state first
[ https://issues.apache.org/jira/browse/MESOS-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727351#comment-13727351 ]
Vinod Kone commented on MESOS-611:
----------------------------------
https://reviews.apache.org/r/13216/
> Refactor slave recovery to ensure slave recovers its state first
> ----------------------------------------------------------------
>
> Key: MESOS-611
> URL: https://issues.apache.org/jira/browse/MESOS-611
> Project: Mesos
> Issue Type: Bug
> Reporter: Vinod Kone
> Assignee: Vinod Kone
> Fix For: 0.13.0
>
>
> Currently, the slave recovers its state after it sends 'recover' messages to the isolator and status update manager. This means it could potentially receive status updates and executor terminated messages before the slave had a chance to recover its state, which is bad!
--
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