There is no operator API (i.e., http api endpoint in your parlance) to add/kill tasks.
Your job master can talk to the framework that launched all your tasks in the first place (marathon?), to add/kill tasks. Most existing mesos frameworks expose add/kill tasks through their own API. Alternatively, you can rewrite your job master as a Mesos framework <http://mesos.apache.org/documentation/latest/app-framework-development-guide/>. A framework can add/kill tasks through the scheduler api <http://mesos.apache.org/documentation/latest/scheduler-http-api/>. But, this is likely a much bigger undertaking. On Mon, Feb 11, 2019 at 6:15 AM Gurhan Gunduz <gurhangun...@hotmail.com> wrote: > I would be really glad if you could tell me what to do for the following > situation; I am running a job consists of tasks running in docker > containers on agents. One of these tasks is the job master, which decides > when to kill the framework or kill few of the tasks or add new tasks to the > job. I can kill the framework using the endpoint > mesos.apache.org/documentation/latest/endpoints/master/teardown< > http://mesos.apache.org/documentation/latest/endpoints/master/teardown/>. > What should I do in order to add or kill tasks. As I mentioned one of the > tasks(job master) will decide on this dynamically. > Thanks, > Gurhan >
