You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Ravi Prakash (Commented) (JIRA)" <ji...@apache.org> on 2011/10/04 00:30:34 UTC
[jira] [Commented] (MAPREDUCE-3087) CLASSPATH not the same after
MAPREDUCE-2880
[ https://issues.apache.org/jira/browse/MAPREDUCE-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119694#comment-13119694 ]
Ravi Prakash commented on MAPREDUCE-3087:
-----------------------------------------
Ok! So here's what I did. I breakpointed at ContainerLaunch.java:197 (which basically launches the containers). While execution was suspended, I manually edited the task.sh to change mr-app.jar!/mrapp-generated-classpath to simply mr-app.jar.
I had to do this thrice for a simple word-count (once for the AM, once for the map and once for the reduce I guess). This let me job succeed.
Did MR-2880 simplify the expansion of !/mrapp-generated-classpath, or is this some cool JAVA classpath trick that I don't know about?
> CLASSPATH not the same after MAPREDUCE-2880
> -------------------------------------------
>
> Key: MAPREDUCE-3087
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3087
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Ravi Prakash
> Attachments: notworking.classpath.uniq, working.classpath.uniq
>
>
> After MAPREDUCE-2880, my classpath was missing key jar files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira