[
https://issues.apache.org/jira/browse/MESOS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15009544#comment-15009544
]
Adam B commented on MESOS-313:
------------------------------
[~zhitao] You are absolutely correct. The Mesos master needs to send the
message to the SchedulerDriver, if it doesn't already; and the SchedulerDriver
needs to call the existing executorLost callback on the framework's scheduler.
See the SlaveLost/LostSlave messages/methods for a good example.
As [~vinodkone] mentioned, we would like to be able to make this message
reliably delivered, like some of the other StatusUpdate messages, but let's
leave that for a phase 2 and try to get an MVP that at least attempts to notify
the scheduler.
> report executor deaths to framework schedulers
> ----------------------------------------------
>
> Key: MESOS-313
> URL: https://issues.apache.org/jira/browse/MESOS-313
> Project: Mesos
> Issue Type: Improvement
> Reporter: Charles Reiss
> Labels: mesosphere, newbie
>
> 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)
