GitHub user kbzod opened a pull request:

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

    [WIP] SPARK-2450: Add YARN executor log links to UI executors page

    This adds a new column in the Executors page of the Spark UI called "Logs", 
visible only when running under YARN. After getting a container for an 
executor, the YarnAllocationHandler informs the UI of where its logs reside, so 
that a link can be presented in the Logs column for it.
    
    Current issues / limitations:
    * This only works running with yarn-cluster, not yarn-client.
    * The mechanism for getting the log URL through to the UI is different than 
the usual way information gets there (via SparkListeners). There may be a 
better, more decoupled way to do it.
    
    ![screen shot 2014-07-10 at 4 36 28 
pm](https://cloud.githubusercontent.com/assets/1541206/3557128/006f6ea2-092c-11e4-8125-5c2c3a158068.png)

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

    $ git pull https://github.com/kbzod/spark SPARK-2450

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

    https://github.com/apache/spark/pull/1375.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 #1375
    
----
commit f3d42ecf3309e6c3ddd7ffc2fce990776059b414
Author: Bill Havanki <bhava...@cloudera.com>
Date:   2014-07-10T18:28:46Z

    SPARK-2450 Initial prototype.

commit 60cc1121d27f94bbf695763d585b29a8be4023aa
Author: Bill Havanki <bhava...@cloudera.com>
Date:   2014-07-10T19:32:08Z

    SPARK-2450 Better abstraction

commit 57dca648aa30a15525d03d3bbecb85f4340829eb
Author: Bill Havanki <bhava...@cloudera.com>
Date:   2014-07-11T17:59:26Z

    SPARK-2450 Add Javadoc.

----


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

Reply via email to