Re: Subscribe to an active framework through HTTP API Scheduler

Someone worked on it (new operator api call) during the Mesoscon EU hackathon. They were planning to send a review once they wrap it up. On Tue, Oct 31, 2017 at 12:11 PM, Benjamin Mahler wrote: > There had been discussion to support killing tasks from the operator API, > but

Re: Subscribe to an active framework through HTTP API Scheduler

Each active framework on HTTP scheduler API is allocated with a stream id. This is included in the header "Mesos-Stream-Id" in initial subscribed response. If you obtain this stream id, another process can "impersonate" this framework to submit kill requests (using framework id, task id and the

Subscribe to an active framework through HTTP API Scheduler

Hi, We have a framework with some tasks that we would like to kill but not all framework (teardown), so we would like to use the kill method of the http api scheduler, the problem is that is needed to be suscribed. Creating a new framework in stream mode and executing the kill method it's not