You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Dominic Hamon (JIRA)" <ji...@apache.org> on 2014/10/06 23:25:34 UTC

[jira] [Assigned] (MESOS-1869) UpdateFramework message might reach the slave before Reregistered message and get dropped

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

Dominic Hamon reassigned MESOS-1869:
------------------------------------

    Assignee: Yan Xu

> UpdateFramework message might reach the slave before Reregistered message and get dropped
> -----------------------------------------------------------------------------------------
>
>                 Key: MESOS-1869
>                 URL: https://issues.apache.org/jira/browse/MESOS-1869
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Vinod Kone
>            Assignee: Yan Xu
>
> In reregisterSlave() we send 'SlaveReregisteredMessage' before we link the slave pid, which means a temporary socket will be created and used.
> Subsequently, after linking, we send the UpdateFrameworkMessage, which creates and uses a persistent socket.
> This might lead to out-of-order delivery, resulting in UpdateFrameworkMessage reaching the slave before the SlaveReregisteredMessage and getting dropped because the slave is not yet (re-)registered.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)