You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Anand Mazumdar (JIRA)" <ji...@apache.org> on 2016/02/13 03:00:20 UTC

[jira] [Created] (MESOS-4671) Status updates from executor can be forwarded out of order by the Agent.

Anand Mazumdar created MESOS-4671:
-------------------------------------

             Summary: Status updates from executor can be forwarded out of order by the Agent.
                 Key: MESOS-4671
                 URL: https://issues.apache.org/jira/browse/MESOS-4671
             Project: Mesos
          Issue Type: Bug
          Components: containerization, HTTP API
    Affects Versions: 0.28.0
            Reporter: Anand Mazumdar


Previously, all status update message from the executor were forwarded by the agent to the master in the order that they had been received. 

However, that seems to be no longer valid due to a recently introduced change in the agent:

{code}
// Before sending update, we need to retrieve the container status.
  containerizer->status(executor->containerId)
    .onAny(defer(self(),
                 &Slave::_statusUpdate,
                 update,
                 pid,
                 executor->id,
                 lambda::_1));
{code}

This can sometimes lead to status updates being sent out of order depending on the order the {{Future}} is fulfilled from the call to {{status(...)}}.



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