Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10700#issuecomment-171442415
Will this change still be relevant if we remove the Spark Master's embedded
HistoryServer? In other words, does this race condition affect the standalone
HistoryServer or only the Master history server? If it only affects the master
then this isn't worth changing in master since we're going to remove the
master's embedded history server for Spark 2.0. It may still be worthwhile for
Spark 1.6, though, although there's a risk/benefit trade-off here.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
