hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-449) MRAppMaster classpath not set properly for unit tests in downstream projects
Date Sun, 10 Mar 2013 15:39:13 GMT

    [ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598288#comment-13598288

Ted Yu commented on YARN-449:

I tried 3 methods which resulted in different mapreduce jobs to fail.

1. copy JobConf returned from MiniMRCluster.getJobConf() to HBaseTestingUtility.conf
here is test result based on hadoop 1.0 (org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat

2. extract config entries from MiniMRCluster.getJobConf() which are absent in HBaseTestingUtility.conf
and put them in HBaseTestingUtility.conf
mapreduce.TestRowCounter failed building against hadoop 2.0:

3. extract all config entries from MiniMRCluster.getJobConf() and put them in HBaseTestingUtility.conf
mapreduce.TestImportExport failed building against hadoop 2.0:
> MRAppMaster classpath not set properly for unit tests in downstream projects
> ----------------------------------------------------------------------------
>                 Key: YARN-449
>                 URL: https://issues.apache.org/jira/browse/YARN-449
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.0.3-alpha
>            Reporter: Siddharth Seth
>            Priority: Blocker
>         Attachments: 7904-v5.txt, hbase-7904-v3.txt, hbase-TestHFileOutputFormat-wip.txt,
> Post YARN-429, unit tests for HBase continue to fail since the classpath for the MRAppMaster
is not being set correctly.
> Reverting YARN-129 may fix this, but I'm not sure that's the correct solution. My guess
is, as Alexandro pointed out in YARN-129, maven classloader magic is messing up java.class.path.

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

View raw message