mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jie Yu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-4671) Status updates from executor can be forwarded out of order by the Agent.
Date Wed, 17 Feb 2016 23:07:18 GMT

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

Jie Yu updated MESOS-4671:
--------------------------
    Fix Version/s: 0.28.0

> 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
>            Assignee: Avinash Sridharan
>            Priority: Blocker
>              Labels: mesosphere
>             Fix For: 0.28.0
>
>
> Previously, all status update messages 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)

Mime
View raw message