Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Sun, 7 Jul 2013 21:35:48 +0000 (UTC)
From: "Benjamin Mahler (JIRA)" <jira@apache.org>
To: mesos-dev@incubator.apache.org
Message-ID: <JIRA.12644418.1366829732942.9202.1373232948953@arcas>
In-Reply-To: <JIRA.12644418.1366829732942@arcas>
References: <JIRA.12644418.1366829732942@arcas>
Subject: [jira] [Updated] (MESOS-451) Always update resources for
 re-registered executors.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Benjamin Mahler updated MESOS-451:
----------------------------------

    Fix Version/s: 0.13.0
    
> Always update resources for re-registered executors.
> ----------------------------------------------------
>
>                 Key: MESOS-451
>                 URL: https://issues.apache.org/jira/browse/MESOS-451
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Benjamin Mahler
>            Assignee: Vinod Kone
>             Fix For: 0.13.0
>
>
> Given the presence of the --cgroups_enable_cfs flag, we will want to ensure that all recovered executors have hard cpu limiting retroactively applied to them after recovery.
> Currently, since we only call Isolator::resourcesChanged() when there are pending status updates, we *sometimes* retroactively enforce hard limiting.
> It would be better to always call Isolator::resourcesChanged() when executors re-register to ensure we keep things consistent.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira