[
https://issues.apache.org/jira/browse/MESOS-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923042#comment-13923042
]
Benjamin Mahler commented on MESOS-544:
---------------------------------------
We're not going to provide the notion of being "drained soon" in this first
approach as that requires persistent information in the Master. It's part of
what I'm looking to explore in (3), what benefits does this afford frameworks
vs the increased system complexity.
For now, the goal is to provide a way to "drain now", which we currently don't
have.
> Mesos-slave support for "node drain"
> ------------------------------------
>
> Key: MESOS-544
> URL: https://issues.apache.org/jira/browse/MESOS-544
> Project: Mesos
> Issue Type: Story
> Components: framework, master, slave
> Reporter: Tobias Weingartner
> Labels: gsoc2014
> Fix For: 0.19.0
>
>
> Given that multiple frameworks can be present on a machine at a time, and
> writing "node drain" for each possible framework is an intractable task, it
> would nice if the slave-master core had a means to tell frameworks that tasks
> were killed to drain a host. Or possibly that the slave was told to drain
> the host of all tasks (graceful shutdown, etc).
> {noformat}
> # drain current host
> pkill -USR1 mesos-slave
> {noformat}
> This would make writing scripts for site-ops to do node maintenance much
> easier... :)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
