Mailing-List: contact mesos-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mesos-dev@incubator.apache.org
Date: Wed, 8 May 2013 07:09:16 +0000 (UTC)
From: "Benjamin Mahler (JIRA)" <jira@apache.org>
To: mesos-dev@incubator.apache.org
Message-ID: <JIRA.12644017.1366672397135.286359.1367996956129@arcas>
In-Reply-To: <JIRA.12644017.1366672397135@arcas>
References: <JIRA.12644017.1366672397135@arcas>
Subject: [jira] [Resolved] (MESOS-446) Master should shutdown slaves that
 were deactivated
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Benjamin Mahler resolved MESOS-446.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.12.0
    
> Master should shutdown slaves that were deactivated
> ---------------------------------------------------
>
>                 Key: MESOS-446
>                 URL: https://issues.apache.org/jira/browse/MESOS-446
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Vinod Kone
>            Assignee: Benjamin Mahler
>             Fix For: 0.12.0
>
>
> When a master receives any message from a deactivated slave, master should send a shutdown message. This is because the master has told the frameworks that the slave was lost and all its tasks were potentially rescheduled by the frameworks.

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