Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/1358#issuecomment-55978678
I see, so maybe the problem is that an executor dies, and another is
launched on the same Mesos machine with the same executor ID, which then breaks
assumptions elsewhere in the code. In that case, our executor ID would need to
be something like (Mesos executor ID) + (our attempt # on this executor). But
you'd need to look throughout the MesosScheduler code and make sure this works
-- in particular we have to send back the right ID when we launch tasks.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
