GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/3183
Fix link issue of the executor thread dump page in yarn-cluster mode
In yarn-cluster mode, the Web UI is running behind a yarn proxy server.
Some features(or bugs?) of yarn proxy server will break the links for thread
dump.
1. Yarn proxy server will do http redirect internally, so if opening
`http://example.com:8088/cluster/app/application_1415344371838_0012/executors`,
it will fetch
`http://example.com:8088/cluster/app/application_1415344371838_0012/executors/`
and return the content but won't change the link in the browser. Then when a
user clicks `Thread Dump`, it will jump to
`http://example.com:8088/proxy/application_1415344371838_0012/threadDump/?executorId=2`.
This is a wrong link. The correct link should be
`http://example.com:8088/proxy/application_1415344371838_0012/executors/threadDump/?executorId=2`.
2. Yarn proxy server has a bug about the URL encode/decode. When a user
accesses
`http://example.com:8088/proxy/application_1415344371838_0006/executors/threadDump/?executorId=%3Cdriver%3E`,
the yarn proxy server will require
`http://example.com:36429/executors/threadDump/?executorId=%25253Cdriver%25253E`.
But Spark web server expects
`http://example.com:36429/executors/threadDump/?executorId=%3Cdriver%3E`. I
will report this issue to Hadoop community later.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zsxwing/spark SPARK-4313
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/3183.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3183
----
commit abfa063ada8b7c34f842f156e26002537aaa4883
Author: zsxwing <[email protected]>
Date: 2014-11-10T06:47:55Z
Fix link issue of the executor thread dump page in yarn-cluster mode
----
---
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]
