Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2432#issuecomment-56281779
Quoting @sarutak from #2250, regarding this PR:
> And for problem 2, when launching ExecutorBackends, launcher pass
application id to ExecutorBackends. It doesn't consider Mesos because
MesosSchedulerBackend doesn't return application id so if we use Mesos,
System.currentTimeMillis is used instead of application id.
Is there a good reason _why_ the Mesos backend doesn't return an
application ID? Can we modify it to generate a unique ID for us?
---
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
