GitHub user ehnalis opened a pull request:

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

    [SPARK-8016] YARN cluster / client modes have different app names for python

    [SPARK-8016] YARN cluster / client modes have different app names for python
    
    Cause: Currently in YARN the only point where the name of the application 
can be set is when it gets submitted by the client. In yarn-cluster mode this 
is performed by the spark-submit, which uses 
org.apache.spark.deploy.yarn.Client. The name of the application is picked from 
--name, or by default from --class. In case of yarn-client mode, the name of 
the application is set by SparkContext.setAppName.
    
    Solution: It is not feasible to read the name set with 
SparkContext.setAppName in yarn-cluster mode. Added additional notes to the 
arguments list of spark-submit.

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

    $ git pull https://github.com/ehnalis/spark app-names

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

    https://github.com/apache/spark/pull/6671.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 #6671
    
----
commit 0409b5cac0eda77881e0ede74404b922a3d29615
Author: ehnalis <[email protected]>
Date:   2015-06-05T12:05:24Z

    [SPARK-8016] YARN cluster / client modes have different app names for python
    
    Cause: Currently in YARN the only point where the name of the application 
can be set is when it gets submitted by the client. In yarn-cluster mode this 
is performed by the spark-submit, which uses 
org.apache.spark.deploy.yarn.Client. The name of the application is picked from 
--name, or by default from --class. In case of yarn-client mode, the name of 
the application is set by SparkContext.setAppName.
    
    Solution: It is not feasible to read the name set with 
SparkContext.setAppName in yarn-cluster mode. Added additional notes to the 
arguments list of spark-submit.

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

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

Reply via email to