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/14 20:10:48 UTC

[jira] [Resolved] (MESOS-637) Executor should re-register with the updates in the same order as it received them

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

Vinod Kone resolved MESOS-637.
------------------------------

    Resolution: Fixed
    
> Executor should re-register with the updates in the same order as it received them
> ----------------------------------------------------------------------------------
>
>                 Key: MESOS-637
>                 URL: https://issues.apache.org/jira/browse/MESOS-637
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Vinod Kone
>            Assignee: Vinod Kone
>             Fix For: 0.14.0
>
>
> Currently the updates are stored in a hashmap inside the executor driver, which means the order of the updates is lost. This might result in a slave getting a non-terminal update after a terminal update, when the executor reregisters!

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