[ https://issues.apache.org/jira/browse/MESOS-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Mahler closed MESOS-544. --------------------------------- Resolution: Duplicate Thanks for the feedback everyone! After many discussions we have a better idea of the kinds of primitives that will be needed to provide framework agnostic maintenance primitives in Mesos. As a result, I'm moving this to a cleaner, more formalized epic to track all the maintenance related work: MESOS-1474 > 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 > > 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)