hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Duxbury (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-536) Remove MiniDFS startup from MiniHBaseCluster
Date Fri, 21 Mar 2008 23:59:24 GMT

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

Bryan Duxbury updated HBASE-536:

    Attachment: 536.patch

Here's a patch that reorders things somewhat. 

Of note is that HBaseClusterTestCase is much changed. Check out the *Setup methods to get
a sense of how things work. MiniHBaseCluster has been left alone for the moment, but there's
a parallel class called MiniHBaseCluster2 that works exactly the same way, except it lets
HBaseClusterTestCase do the MiniDFS work. 

The plan is to remove the original MiniHBase and replace it with the version 2. The only thing
that is holding me back at the moment is PerformanceEvaluation.java, which throws some weird
error for me pertaining to MiniDFS trying to find its web apps. Every other test has been
ported to correctly use HBaseTestCase instead of managing its own MiniDFS and MiniHBase. 

If someone could take a look at the problems with PE (when running with --miniCluster, of
course), then we can commit this. 

> Remove MiniDFS startup from MiniHBaseCluster
> --------------------------------------------
>                 Key: HBASE-536
>                 URL: https://issues.apache.org/jira/browse/HBASE-536
>             Project: Hadoop HBase
>          Issue Type: New Feature
>          Components: test
>            Reporter: Bryan Duxbury
>            Assignee: Bryan Duxbury
>            Priority: Minor
>             Fix For: 0.2.0
>         Attachments: 536.patch
> Change MiniHBaseCluster to always require a MiniDfs started elsewhere. It will decide
where to read and write based on the config passed in to its constructor. 
> HBaseClusterTestCase will be updated to do the MiniDFS spinup and shutdown as part of
its normal process.
> Completing this issue will prime us for solving the truly external DFS issue for making
the test suite faster. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message