[
https://issues.apache.org/jira/browse/MESOS-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912457#comment-13912457
]
Benjamin Mahler commented on MESOS-544:
---------------------------------------
Providing a bit more context here for gsoc students.
Currently, if an operator wants to take a slave or it's machine offline, they
can kill the slave via SIGTERM. This will, however, leave all tasks running on
the machine. Normally, a new slave is started and will clean these up. But, in
the case where there is no intent to start a new slave in a timely manner, it
should be possible to kill the slave in a way that will kill the underlying
tasks.
We could accomplish this by implementing a SIGUSR1 handler that will perform a
clean shutdown. This would involve killing all the tasks running on the slave.
Ideally, this could inform the Master about the tasks being killed.
> 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
> 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.1.5#6160)
