Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2944#issuecomment-60845020
I like the idea of running a separate UI server on the executor, but this
seems like a much more involved change that will take a lot more design review.
For example, we'd have to consider how those web UIs will be secured, which
ports they will bind to, etc.
As a shorter-term fix, how about de-coupling the thread dumps from the
heartbeats so that huge thread dumps won't cause heartbeats to be lost? If we
do this, I might be able to add a driver -> executor RPC path to allow
heartbeats to be triggered from the web UI.
---
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]
