mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominic Hamon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-1869) UpdateFramework message might reach the slave before Reregistered message and get dropped
Date Mon, 06 Oct 2014 21:25:35 GMT

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

Dominic Hamon updated MESOS-1869:
---------------------------------
    Shepherd: Vinod Kone

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

Mime
View raw message