[ https://issues.apache.org/jira/browse/HADOOP-8899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478665#comment-13478665
]
Alejandro Abdelnur commented on HADOOP-8899:
--------------------------------------------
Suresh, my bad, I was missing the MANIFEST.MF *Class-path:* trick. Now it makes sense, no
objection. I have not look at the patch but conceptually seems OK. Just make sure all paths
to JARs listed in the *Class-path:* are relative to the location of the manifest only JAR
and there are not ../ in the paths. In other words, all the JARs mentioned in the manifest
only JAR must be in the same directory or in a subdirectory from where the manifest only JAR
is. Thx
> Classpath exceeds maximum OS limit
> ----------------------------------
>
> Key: HADOOP-8899
> URL: https://issues.apache.org/jira/browse/HADOOP-8899
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 1-win
> Reporter: Ahmed El Baz
> Attachments: HADOOP-8899.branch-1-win.classpath.patch
>
>
> We hit errors in TT due to long classpath value. One example is Oozie trying to start
a hive job, and it fails with the following error:
> java.io.IOException: Command exceeds the OS command length limit: 8192, command: "set
CLASSPATH="….
> The classpath includes Hadoop Core + Hive Jars which are in the distributed cache. This
is causing the classpath to be too long giving the error above. A viable long term fix is
to generate a temporary JAR file in the task cache directory which includes all elements in
the long classpath, and then provide this as the "-classpath" argument for the JVM to be spawned.
This is gated for Windows only.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|