mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Vivien <vladimir.viv...@gmail.com>
Subject Re: Mesos Scheduler/Executor coordination mechanism
Date Thu, 26 Sep 2013 19:26:44 GMT
Vinod
Thanks.  Your reply added more knowledge to my understanding.

>From my one week understanding of mesos, it seems when a slave launches a
task, it does so via an OS call of "/bin/sh -c".  Now, how does the slave
process reach into the running process to trigger the callbacks ?


On Thu, Sep 26, 2013 at 3:17 PM, Vinod Kone <vinodkone@gmail.com> wrote:

> The way it works is as follows:
>
> Scheduler launches "tasks". A task has an "executor id" (optional)
> attached to it. When a slave gets a task, it launches an executor if an
> executor with that "executor id" is not running. All subsequent tasks
> tagged with the same "executor id" are just passed on to the running
> executor.
>
> Typically executors send TASK_STARTING or TASK_RUNNING updates when a task
> gets launched. This is the signal that could be used by the schedulers to
> know that a task (and its corresponding executor) has launched.
>
> HTH,
>
>
> On Thu, Sep 26, 2013 at 12:03 PM, Vladimir Vivien <
> vladimir.vivien@gmail.com> wrote:
>
>> Hi.  New to Mesos and still trying to wrap my head around its concept.
>>
>> Question:
>> When an executor is launched by Mesos, how does the Scheduler know about
>> the Executor it just launched and vise versa ?  It appears that the slave
>> launches an OS process, but I am unclear how the coordination is done
>> between the running OS process and mesos.
>>  --
>> Vladimir Vivien
>>
>
>


-- 
Vladimir Vivien

Mime
View raw message