Return-Path: X-Original-To: apmail-mesos-issues-archive@minotaur.apache.org Delivered-To: apmail-mesos-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A2EF218708 for ; Wed, 17 Feb 2016 23:07:18 +0000 (UTC) Received: (qmail 52404 invoked by uid 500); 17 Feb 2016 23:07:18 -0000 Delivered-To: apmail-mesos-issues-archive@mesos.apache.org Received: (qmail 52361 invoked by uid 500); 17 Feb 2016 23:07:18 -0000 Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list issues@mesos.apache.org Received: (qmail 52258 invoked by uid 99); 17 Feb 2016 23:07:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Feb 2016 23:07:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 3B9E92C1F62 for ; Wed, 17 Feb 2016 23:07:18 +0000 (UTC) Date: Wed, 17 Feb 2016 23:07:18 +0000 (UTC) From: "Jie Yu (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MESOS-4671) Status updates from executor can be forwarded out of order by the Agent. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)