Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1778525896.1204920466723.JavaMail.jira@brutus>
Date: Fri, 7 Mar 2008 12:07:46 -0800 (PST)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-498) Use an external DFS instead of
 spinning up a MiniDFS for every test
In-Reply-To: <1930418979.1204853097961.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-498:
-----------------------------

Great.  We can call this at end of test?  Shall we start in on a refactor of tests that cuts out spin up of minidfs and that instead just reads the filesystem to use from $HBASE_HOME/src/test/hbase-site.xml?  (On hudson can fill this file w/ the hdfs to use)

> Use an external DFS instead of spinning up a MiniDFS for every test
> -------------------------------------------------------------------
>
>                 Key: HBASE-498
>                 URL: https://issues.apache.org/jira/browse/HBASE-498
>             Project: Hadoop HBase
>          Issue Type: Sub-task
>          Components: test
>            Reporter: Bryan Duxbury
>             Fix For: 0.2.0
>
>
> My testing suggests that we could shave about a minute off the entire suite if we only had to start up a single DFS instance instead of a new one for each test. Stack has investigated using ant to perform this initialization task, but come up empty handed.
> I propose that we should expect the developer running the test suite to start a DFS before running "ant test". We could provide a bin/hbase command that does specifically that in order to make it easy. This would save not only the initial start up time but all the startup time of all tests and test suite runs you execute in a session of development and testing. 
> Do people think that an extra step to testing would be too hard for new (or lazy existing) developers?

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