hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-498) [testing] Use an external DFS instead of spinning up a MiniDFS for every test
Date Fri, 16 Oct 2009 03:06:31 GMT

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

stack resolved HBASE-498.
-------------------------

    Resolution: Duplicate

Running a dfscluster for length of test is what hbase-410 is about.  Marking this closed as
duplicate.

> [testing] 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
>    Affects Versions: 0.2.0
>            Reporter: Bryan Duxbury
>            Priority: Minor
>             Fix For: 0.21.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.


Mime
View raw message