You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Patrick Wendell (JIRA)" <ji...@apache.org> on 2014/05/10 03:12:40 UTC
[jira] [Resolved] (SPARK-1631) App name set in SparkConf (not in
JVM properties) not respected by Yarn backend
[ https://issues.apache.org/jira/browse/SPARK-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Wendell resolved SPARK-1631.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
Issue resolved by pull request 539
[https://github.com/apache/spark/pull/539]
> App name set in SparkConf (not in JVM properties) not respected by Yarn backend
> -------------------------------------------------------------------------------
>
> Key: SPARK-1631
> URL: https://issues.apache.org/jira/browse/SPARK-1631
> Project: Spark
> Issue Type: Bug
> Components: YARN
> Affects Versions: 1.0.0
> Reporter: Marcelo Vanzin
> Assignee: Marcelo Vanzin
> Priority: Blocker
> Fix For: 1.0.0
>
>
> When you submit an application that sets its name using a SparkContext constructor or SparkConf.setAppName(), the Yarn app name is not set and the app shows up as "Spark" in the RM UI.
> That's because YarnClientSchedulerBackend only looks at the system properties to look for the app name, instead of looking at the app's config.
> e.g., app initializes like this:
> {code}
> val sc = new SparkContext(new SparkConf().setAppName("Blah"));
> {code}
> Start app like this:
> {noformat}
> ./bin/spark-submit --master yarn --deploy-mode client blah blah blah
> {noformat}
> And app name in RM UI does not reflect the code.
--
This message was sent by Atlassian JIRA
(v6.2#6252)