[
https://issues.apache.org/jira/browse/MESOS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299250#comment-14299250
]
Ben Whitehead commented on MESOS-313:
-------------------------------------
I recently ran into this issue when working on developing a framework to run
Cassandra.
I had to figure out a work around of starting a no-op task (with some special
data in it so I can track it) so that I could track that the executor was still
running. If this no-op task is ever lost I assume the executor is lost with it
and I can then try and recover from there.
It's quite confusing that {executorLost} is in the API and the behavior is
documented (at least on the Java interface) when it isn't implemented.
> 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
>
> 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)
