hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (YARN-449) HBase test failures when running against Hadoop 2
Date Mon, 01 Apr 2013 20:49:15 GMT

     [ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Siddharth Seth resolved YARN-449.

       Resolution: Fixed
    Fix Version/s: 2.0.4-alpha

Summarizing for reference, and closing this since HBASE-7904 is committed.
Critical fixes to YARN
  YARN-429 fixes capacity-scheduler.conf being unavailable.
Additional fixes which (in most cases) don't affet HBASE, but could affect other projects
using the MiniMRCluster
  YARN-470 and MAPREDUCE-5094 (wip) - disable memory monitoring by default in the MiniMRYARNCluster
  MAPREDUCE-5083 - Randomize MiniMRCluster directory component, to allow parallel instances

Changes to HBase (HBASE-7904)
  Fixes to TestImportExport to copy yarn configuration in all cases.
  Changes to HBaseTestingUtility to merge the configuration returned by MiniMRCluster.
  Chane to HRegion to not use a 'CompoundConfiguration' when talking to HDFS, due to the inability
to change the RPC engine with CompoundConfiguration. (Causes several *SecureLoad tests to
> HBase test failures when running against Hadoop 2
> -------------------------------------------------
>                 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
>             Fix For: 2.0.4-alpha
>         Attachments: 7904-v5.txt, hbase-7904-v3.txt, hbase-TestHFileOutputFormat-wip.txt,
hbase-TestingUtility-wip.txt, minimr_randomdir-branch2.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