[
https://issues.apache.org/jira/browse/MESOS-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029938#comment-14029938
]
Adam B commented on MESOS-1476:
-------------------------------
This can currently be (hackily) supported by updating the whitelist file used
by mesos-master --whitelist=_path_
An observer reads this file regularly, so removing a slave hostname from the
whitelist will prevent its resources from being offered.
I agree that actual deactivate/activate endpoints would be smoother, and
wouldn't require a full whitelist for the cluster, but I just want to point out
that there is a workaround already, in case you want to work on draining tasks
from the slave first.
> 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
> Assignee: Alexandra Sava
> 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.2#6252)
