See also https://issues.apache.org/jira/browse/MESOS-155 for "preemption" and the "inverse offer" mechanism in https://issues.apache.org/jira/browse/MESOS-1474 (Maintenance Primitives)
On Tue, Feb 24, 2015 at 10:00 AM, Vinod Kone <[email protected]> wrote: > > Not currently, no. But we've definitely discussed these semantics ( >> https://issues.apache.org/jira/browse/MESOS-354). The timeline for this >> feature is not clear yet. >> >> On Tue, Feb 24, 2015 at 9:23 AM, dev middleware <[email protected] >> > wrote: >> >>> Thanks. Can this also be done by the master (resource allocation >>> module)? It might be required to kill a task belonging to a misbehaving >>> framework. Or to implement a centrally enforced policy that can stop low >>> priority jobs from one framework, in order to make room for high priority >>> jobs from another framework. >>> >>> On Tue, Feb 24, 2015 at 6:19 PM, Vinod Kone <[email protected]> wrote: >>> >>>> There's a killTask() call frameworks can use. >>>> >>>> @vinodkone >>>> >>>> > On Feb 24, 2015, at 7:42 AM, dev middleware <[email protected]> >>>> wrote: >>>> > >>>> > Hi, >>>> > >>>> > I'm new to Mesos technology. Browsing thru the documentation, I >>>> couldn't find how a running task can be killed by Mesos master (/ its >>>> pluggable resource allocation module), or by a framework on top of Mesos. >>>> Is it possible with current Mesos tools, or a task stops only when it is >>>> finished? If latter, are there plans to support task preemption in future >>>> versions? >>>> > >>>> > Thanks, Benny >>>> >>> >>> >> >
