You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Gautham Banasandra (Jira)" <ji...@apache.org> on 2022/12/04 10:33:00 UTC
[jira] [Commented] (YARN-11386) Fix issue with classpath resolution
[ https://issues.apache.org/jira/browse/YARN-11386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642973#comment-17642973 ]
Gautham Banasandra commented on YARN-11386:
-------------------------------------------
This issue is caused by YARN-10664. The call to *[expandAllEnvironmentVars|https://github.com/apache/hadoop/blob/60e0fe87094771b3188b9b1cd4bf7acf54d40ab7/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/launcher/ContainerLaunch.java#L348]* must happen before invoking *[sanitizeEnv|https://github.com/apache/hadoop/blob/60e0fe87094771b3188b9b1cd4bf7acf54d40ab7/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/launcher/ContainerLaunch.java#L344-L346]*.
> Fix issue with classpath resolution
> -----------------------------------
>
> Key: YARN-11386
> URL: https://issues.apache.org/jira/browse/YARN-11386
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 3.4.0
> Environment: Windows 10
> Reporter: Gautham Banasandra
> Assignee: Gautham Banasandra
> Priority: Critical
>
> While launching the AM, the client puts the classpath into environment HashMap of the ContainerLaunchContext. To support cross-platform compatibility, some special notations must be used by the client. For example, <CPS> must be used as the classpath separator instead of ";" (Windows) or ":" (Linux). The NM would resolve all the <CPS> using the appropriate path separator according to the OS platform, prior to launching the container. In addition to this, the NM is also expected to expand and resolve all of the wildcard ( * ) occurrences in the classpath before launching the container, since the JVM doesn't understand the wildcard charater.
> The issue we see here is, neither <CPS> resolution nor wildcard expansion is happening.
> I tested this from Spark. To run a Spark application on YARN, one needs to set the *spark.yarn.jars* config to point to the location where Spark jars are present. NM would then add these jars to the classpath before launching the Spark AM container. The resolution didn't happen -
> {code}
> Manifest-Version:
> 1.0
> Class-Path:
> file:/D:/tmp/hadoop-Gautham/nm-local-dir/usercache/Gautham/appcache/application_1670138957874_0001/container_1670138957874_0001_01_000001/%7B%7BPWD%7D%7D%3CCPS%3E%7B%7BPWD%7D%7D/__spark_conf__%3CCPS%3E%7B%7BPWD%7D%7D/__spark_libs__/*%3CCPS%3E/D:/projects/github/apache/spark/jars/*%3CCPS%3E%7B%7BPWD%7D%7D/__spark_conf__/__hadoop_conf__
> file:/D:/tmp/hadoop-Gautham/nm-local-dir/usercache/Gautham/appcache/application_1670138957874_0001/container_1670138957874_0001_01_000001/__spark_conf__/
> file:/D:/tmp/hadoop-Gautham/nm-local-dir/usercache/Gautham/appcache/application_1670138957874_0001/container_1670138957874_0001_01_000001/__app__.jar
> {code}
> Note that %3CCPS%3E in the above code block should've been replaced by ";" or ":". Since this didn't happen, NM failed to launch the Spark AM container -
> {code}
> Could not find or load main class org.apache.spark.deploy.yarn.ApplicationMaster
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org