Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/1056#issuecomment-46650373
I've pushed a little further on this, and I'm a little confused about the
right way to proceed with respect to Mesos.
Currently statusUpdates go through the ExecutorBackend interface. My plan
was to add heartbeats to this interface as well. With the
CoarseGrainedExecutorBackend, statusUpdates and other RPCs go to the driver
through actors. So adding a heartbeat message is relatively straightforward.
But with the MesosExecutorBackend, statusUpdates go through a Mesos-specific
interface and RPC framework that I don't see how to add a message to.
Any guidance on the right thing to do here? One option would be to have an
actor separate from the ExecutorBackend interface responsible just for
heartbeats. It would route them to the scheduler and BlockManagerMaster.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
