Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Tue, 9 Sep 2014 00:55:29 +0000 (UTC)
From: "Benjamin Mahler (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12720943.1402599959000.22983.1410224129257@Atlassian.JIRA>
In-Reply-To: <JIRA.12720943.1402599959000@Atlassian.JIRA>
References: <JIRA.12720943.1402599959000@Atlassian.JIRA>
 <JIRA.12720943.1402599959370@arcas>
Subject: [jira] [Updated] (MESOS-1476) Provide endpoints for deactivating /
 activating slaves.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Benjamin Mahler updated MESOS-1476:
-----------------------------------
    Sprint:   (was: Mesos Q3 Sprint 5)

> Provide endpoints for deactivating / activating slaves.
> -------------------------------------------------------
>
>                 Key: MESOS-1476
>                 URL: https://issues.apache.org/jira/browse/MESOS-1476
>             Project: Mesos
>          Issue Type: Improvement
>          Components: master
>            Reporter: Benjamin Mahler
>              Labels: gsoc2014
>
> When performing maintenance operations on slaves, it is important to allow these slaves to be drained of their tasks.
> The first essential primitive of draining slaves is to prevent them from running more tasks. This can be achieved by "deactivating" them: stop sending their resource offers to frameworks.


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