hbase-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] (HBASE-7904) Make mapreduce jobs pass based on 2.0.4-alpha
Date Fri, 29 Mar 2013 20:45:16 GMT

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

Ted Yu commented on HBASE-7904:

I looked at the changes in hadoop-2 branch in the past week.
There were fixes to CapacityScheduler but I think they may not be directly related to the
test failures we saw.

bq. Or is it just this config. manipulation that was needed
I think so.

bq. Where do you think cluster gets its config from? Isn't it using UTIL.getConfiguration?
We obtain cluster at the beginning of the test:
  public static void beforeClass() throws Exception {
    cluster = UTIL.startMiniCluster();
Config manipulation happens in UTIL.startMiniMapReduceCluster().
But startMiniCluster() only calls startMiniDFSCluster(), startMiniZKCluster() and startMiniHBaseCluster(),
in that order.

This is why a little extra manipulation is needed in the tests of TestImportExport.
> Make mapreduce jobs pass based on 2.0.4-alpha
> ---------------------------------------------
>                 Key: HBASE-7904
>                 URL: https://issues.apache.org/jira/browse/HBASE-7904
>             Project: HBase
>          Issue Type: Task
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>            Priority: Critical
>             Fix For: 0.95.0
>         Attachments: 7904.txt, 7904-v2-hadoop-2.0.txt, 7904-v2.txt, 7904-v4-hadoop-2.0.txt,
7904-v4.txt, 7904-v4.txt, 7904-v5-hadoop-2.0.txt, 7904-v5.txt, 7904-v6-hadoop-2.0.txt, 7904-v7-hadoop-2.0.txt,
7904-v8-hadoop-2.0.txt, 7904-v8.txt, 7904-v9-hadoop-2.0.txt, 7904-v9.txt, hbase-7904-v3.txt
> 2.0.3-alpha has been released.
> We should upgrade the dependency.

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