Re: Can't really understand how do Executors can be injected...

Task contains information about resources for an executor [1] by default its 0.1 CPU and 32 MEM [2] 1: https://github.com/apache/mesos/blob/1.4.1/include/mesos/mesos.proto#L736 2: https://github.com/apache/mesos/blob/1.4.1/src/slave/constants.hpp#L101-L105 czw., 23 lis 2017 o 10:15 użytkownik

Re: Can't really understand how do Executors can be injected...

A-ha. This means that there is no resources reservation for an executor, resources are totally dedicated to tasks, correct? On 22 November 2017 at 22:20, Vinod Kone wrote: > If you have an executor running on a agent, wait for an offer from *that > agent* and launch a

Re: Can't really understand how do Executors can be injected...

If you have an executor running on a agent, wait for an offer from *that agent* and launch a new task with the *same* ExecutorInfo as the one you originally used to launch the executor. In this case, mesos will not launch a new executor but passes the task to the already running executor. Note

Re: Can't really understand how do Executors can be injected...

Vihod, much more clear. Thanks. I refined first question inline. On 22 November 2017 at 21:15, Vinod Kone wrote: > Hi Alex, > > See my answers below > > 1. Launch a task without accepting an offer (on already existing executor). >> > > This is not currently possible.

Re: Can't really understand how do Executors can be injected...

Hi Alex, See my answers below 1. Launch a task without accepting an offer (on already existing executor). > This is not currently possible. Every task needs some non-zero resources, and hence an offer, to be launched. What's your use case? > 2. Initiate an executor with no tasks (to launch

Can't really understand how do Executors can be injected...

Hey, I've read Scheduler HTTP API http://mesos.apache.org/documentation/latest/scheduler-http-api/ and do not see how to (what is a call for): 1. Launch a task without accepting an offer (on already existing executor). 2. Initiate an executor with no tasks (to launch them later). 3. How actually