[
https://issues.apache.org/jira/browse/SPARK-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276429#comment-14276429
]
WangTaoTheTonic commented on SPARK-3678:
----------------------------------------
In SparkHdfsLR there has {quote}val sparkConf = new
SparkConf().setAppName("SparkHdfsLR"){quote}.
And in client mode, the register to yarn happens in YarnClientSchedulerBackend,
which is after the setAppName above.
While in cluster mode, the register happens in yarn.Client, which is before
setAppName above.
So it is the register sequence that makes the difference.
> Yarn app name reported in RM is different between cluster and client mode
> -------------------------------------------------------------------------
>
> Key: SPARK-3678
> URL: https://issues.apache.org/jira/browse/SPARK-3678
> Project: Spark
> Issue Type: Bug
> Components: YARN
> Affects Versions: 1.1.0
> Reporter: Thomas Graves
>
> If you launch an application in yarn cluster mode the name of the application
> in the ResourceManager generally shows up as the full name
> org.apache.spark.examples.SparkHdfsLR. If you start the same app in client
> mode it shows up as SparkHdfsLR.
> We should be consistent between them.
> I haven't looked at it in detail, perhaps its only the examples but I think
> I've seen this with customer apps also.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
