I've added decommissioning to the use cases on MESOS-1474 <https://issues.apache.org/jira/browse/MESOS-1474>. ;)
On Mon, Jun 30, 2014 at 11:37 PM, Maxime Brugidou <[email protected] > wrote: > Thanks! This is exactly what I was looking for. I am surprised that the > word "decommission" is not in there. > On Jul 1, 2014 2:52 AM, "Adam Bordelon" <[email protected]> wrote: > >> Hi Maxime, >> >> The slave decomissioning feature is in-progress. For updates, see >> https://issues.apache.org/jira/browse/MESOS-1474 and its sub-JIRAs >> MESOS-1475 and MESOS-1476 >> This includes "Provide a way for frameworks to be notified when resources >> are requested to be relinquished. This gives the framework to proactively >> move a task before it is forcibly killed. It also allows the automation of >> operations like: "please drain these slaves within 1 hour."" >> >> Hope that helps! >> -Adam- >> >> >> On Mon, Jun 30, 2014 at 1:44 PM, Maxime Brugidou < >> [email protected]> wrote: >> >>> hi, >>> >>> Is there any task status update that a scheduler can hook to when a >>> slave will be decommissioned? Is there any process to decommission a slave? >>> >>> This is useful when you need to migrate data from the decommissioned >>> slave. I am looking for a sort of status update for tasks running on the >>> slave and the master shouldn't schedule any other task while >>> decommissioning. The slave could be marked as OK for decommission if no >>> tasks are running. >>> >>> Best, >>> Maxime >>> >> >>
