Hi, @Gidon. In fact, when you call framework.killTask. The framework would send a KillTaskMessage contains frameworkId and taskId to Master. And then Master forward this message to Slave. Ask Slave to kill this task.
On Thu, Jul 2, 2015 at 10:18 PM, Gidon Gershinsky <[email protected]> wrote: > Hi, > > We are developing a resource allocation module, using the new plug-in > mechanism (taken directly from Github, thanks Alex, works smooth). > > Our module will need to revoke/kill tasks, eg to make space for more > important ones (say when they call driver.requestResources, and no > resources are available). I know task revocation can't be done currently > from the master/module, but there is a driver API that enables frameworks > to kill their tasks. > > I can implement an out-of-band mechanism, where the module will communicate > with frameworks on a proprietary protocol, and tell them to kill a task. > But I wonder if there is another option for master-framework messaging > (callable from the allocation module), maybe similar to executor-framework > messaging? Or plans to add kill task API in the master/module? > > Thanks, Gidon > -- Best Regards, Haosdent Huang
