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

["Joe Smith (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923035#comment-13923035 ] 

Joe Smith edited comment on MESOS-544 at 3/6/14 8:48 PM:
---------------------------------------------------------

More addressing #3, and not necessarily for the GSOC project (but something to keep in mind during design-time):

I believe frameworks will always need to be involved with "drains/maintenance" as they'll need to make scheduling decisions (such as to defer offers from slaves that are slated to be drained soon) based on this info.


was (Author: yasumoto):
I believe frameworks will always need to be involved with "drains/maintenance" as they'll need to make scheduling decisions (such as to defer offers from slaves that are slated to be drained soon) based on this info.

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