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 19:21:50 UTC

[jira] [Updated] (MESOS-612) Slave should not recover completed executors

     [ https://issues.apache.org/jira/browse/MESOS-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kone updated MESOS-612:
-----------------------------

    Description: 
Currently, the slave recovers all the executors that have been checkpointed. This means it will send ExecutorTerminated messages for all those executors that have completed (terminated and all updates are acked) in the previous slave run(s).

This is tricky to avoid because there is no explicit feedback that the master has received this message.

  was:
Currently, the slave recovers all the executors that have been checkpointed. This means it will send ExecutorTerminated messages for all those executors that have successfully finished in the previous slave run(s).

This is tricky to avoid because there is no explicit feedback that the master has received this message.

        Summary: Slave should not recover completed executors  (was: Slave should not send redundant ExecutorTerminated messages during recovery)
    
> Slave should not recover completed executors
> --------------------------------------------
>
>                 Key: MESOS-612
>                 URL: https://issues.apache.org/jira/browse/MESOS-612
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Vinod Kone
>            Assignee: Vinod Kone
>             Fix For: 0.13.0
>
>
> Currently, the slave recovers all the executors that have been checkpointed. This means it will send ExecutorTerminated messages for all those executors that have completed (terminated and all updates are acked) in the previous slave run(s).
> This is tricky to avoid because there is no explicit feedback that the master has received this message.

--
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