GitHub user JoshRosen opened a pull request:

    https://github.com/apache/spark/pull/4903

    [SPARK-6175] Fix standalone executor log links when ephemeral ports or 
SPARK_PUBLIC_DNS are used

    This patch fixes two issues with the executor log viewing links added in 
Spark 1.3.  In standalone mode, the log URLs might include a port value of 0 
rather than the actual bound port of the UI, which broke the ability to view 
logs from workers whose web UIs had been configured to bind to ephemeral ports.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/JoshRosen/spark SPARK-6175

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/4903.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 #4903
    
----
commit 422a2ef2f27f2e4ee5bfdaea8a26e1775457d386
Author: Josh Rosen <[email protected]>
Date:   2015-03-05T07:47:07Z

    Use conf.getenv to read SPARK_PUBLIC_DNS

commit c250fbeb121d8d30e84e69238a9ce3daf855974f
Author: Josh Rosen <[email protected]>
Date:   2015-03-05T07:48:23Z

    Respect SparkConf in local-cluster Workers.

commit 27918c76697c70b5fc6467775e898eea7b4127cd
Author: Josh Rosen <[email protected]>
Date:   2015-03-05T07:49:17Z

    Add failing unit tests for standalone log URL viewing

commit cfec1353b658d668ace29c3a30d4aa59a3aa9dd3
Author: Josh Rosen <[email protected]>
Date:   2015-03-05T07:51:22Z

    Use webUi.boundPort and publicAddress in log links

----


---
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]

Reply via email to