It depends on the framework, Mesos imposes no rules on the relationship between a task an executor. The framework can specify an Executor ID with the tasks it's submitting, and if two tasks land on the same slave with the same Executor ID, Mesos will take care of ensuring they share the same Executor process.
The slave actually has a queue of task launch operations it manages and tasks are launched in sequence, so if you respond to two offers with the same Executor ID on the same slave in quick succession, the slave will launch only one instance of the executor and send both tasks to it. I hope that helps! Note: Not all tasks have to have executors, in this instance Mesos will transparent launch an Executor on your behalf, one per task. -- Tom Arnfeld Developer // DueDil On Tue, Jun 30, 2015 at 11:08 AM, Hans van den Bogert <[email protected]> wrote: > I have difficulty understanding Mesos’ model. > A framework can, for every accepted resource offer, mention an executor > besides the tasks descriptions it submits to Mesos. However does every use of > offered resources, start a new executor? Thus for instance if the scenario > occurs that two resource offers are used (shortly after each other), which > happen to be of the same slave, then are two executors started at one point? > Or is the second batch of tasks given to the first started executor? > I hope my question is clear, if not, let me know, > Hans van den Bogert
