[jira] [Commented] (MESOS-313) Report executor terminations to framework schedulers.

["Stephan Erb (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431688#comment-15431688 ] 

Stephan Erb commented on MESOS-313:
-----------------------------------

Now that this patch has landed, even a clean shutdown of an executor (with status code 0) is reported to the framework via the {{executorLost}} message. Is this a bug or intentional?

Example log output:
{code}
I0616 13:55:16.580080 16915 master.cpp:4891] Executor 'thermos-role-env-job-0-d94972f8-760e-4bb0-beef-654e2df1f5e0' of framework 20151001-085346-58917130-5050-37976-0000 on slave d4218d85-e294-4405-af4c-80fc7a66f1a4
-S0 at slave(1)@xxxx:5051 (xxxx): exited with status 0
I0616 13:55:16.580286 16915 master.cpp:6540] Removing executor 'thermos-role-env-job-0-d94972f8-760e-4bb0-beef-654e2df1f5e0' with resources cpus(*):0.01; mem(*):128 of framework 20151001-085346-58917130-5050-37976-0000 on slave d4218d85-e294-4405-af4c-80fc7a66f1a4-S0 at slave(1)@xxxx:5051 (xxxx)
{code}




> Report executor terminations to framework schedulers.
> -----------------------------------------------------
>
>                 Key: MESOS-313
>                 URL: https://issues.apache.org/jira/browse/MESOS-313
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Charles Reiss
>            Assignee: Zhitao Li
>              Labels: mesosphere, newbie
>             Fix For: 0.27.0
>
>
> The Scheduler interface has a callback for executorLost, but currently it is never called.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)