You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2013/12/03 21:11:36 UTC

[jira] [Updated] (MESOS-544) Mesos-slave support for "node drain"

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

Benjamin Mahler updated MESOS-544:
----------------------------------

    Fix Version/s:     (was: 0.16.0)
                   0.17.0

> Mesos-slave support for "node drain"
> ------------------------------------
>
>                 Key: MESOS-544
>                 URL: https://issues.apache.org/jira/browse/MESOS-544
>             Project: Mesos
>          Issue Type: Story
>          Components: documentation, framework, master, slave
>            Reporter: Tobias Weingartner
>             Fix For: 0.17.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.1#6144)