[ 
https://issues.apache.org/jira/browse/SPARK-16966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413852#comment-15413852
 ] 

Weiqing Yang commented on SPARK-16966:
--------------------------------------

Thanks for the quick feedback.

If "--name" is not configured and appName() does not be called,  
"spark.app.name" will be "mainClass"
-------------------------------------------
 // Set name from main class if not given
    name = Option(name).orElse(Option(mainClass)).orNull
------------------------------------------

If "mainClass" is always there, I think removing those three lines of code will 
be safe, but for pyspark and sparkr, the mainclass might be none, is it safe to 
remove those three lines of code? What do you think? [~srowen][~jerryshao]

> App Name is a randomUUID even when "spark.app.name" exists
> ----------------------------------------------------------
>
>                 Key: SPARK-16966
>                 URL: https://issues.apache.org/jira/browse/SPARK-16966
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>            Reporter: Weiqing Yang
>
> When submitting an application with "--name":
> ./bin/spark-submit --name myApplicationTest --verbose --executor-cores 3 
> --num-executors 1 --master yarn --deploy-mode client --class 
> org.apache.spark.examples.SparkKMeans 
> examples/target/original-spark-examples_2.11-2.1.0-SNAPSHOT.jar 
> hdfs://localhost:9000/lr_big.txt 2 5
> In the history server UI:
> App ID: application_1470694797714_0016
> App Name: 70c06dc5-1b99-4b4a-a826-ea27497e977b
> The App Name should not be a randomUUID 
> "70c06dc5-1b99-4b4a-a826-ea27497e977b"  since the "spark.app.name" was 
> myApplicationTest.
> The application "org.apache.spark.examples.SparkKMeans" above did not invoke 
> ".appName()". 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to