You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Andrew Or (JIRA)" <ji...@apache.org> on 2014/09/03 23:59:51 UTC

[jira] [Resolved] (SPARK-3388) Expose cluster applicationId, use it to serve history information

     [ https://issues.apache.org/jira/browse/SPARK-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Or resolved SPARK-3388.
------------------------------
          Resolution: Fixed
       Fix Version/s: 1.2.0
    Target Version/s: 1.2.0

Fixed by https://github.com/apache/spark/pull/1218

> Expose cluster applicationId, use it to serve history information
> -----------------------------------------------------------------
>
>                 Key: SPARK-3388
>                 URL: https://issues.apache.org/jira/browse/SPARK-3388
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 1.1.0
>            Reporter: Marcelo Vanzin
>            Assignee: Marcelo Vanzin
>             Fix For: 1.2.0
>
>
> This is a follow up to SPARK-2150.
> Currently Spark uses the application-generated log directory name as the URL for the history server. That's not very user-friendly since there's no way for the user to figure out that information otherwise.
> A more user-friendly approach would be to use the cluster-defined application id, when present. That also has the advantage of providing that information as metadata for the Spark app, so that someone can easily correlate information kept in Spark with that kept by the cluster manager.
> Open PR: https://github.com/apache/spark/pull/1218



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org