hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4821) A fully automated comprehensive distributed integration test for HBase
Date Wed, 25 Apr 2012 19:32:19 GMT

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

Roman Shaposhnik commented on HBASE-4821:
-----------------------------------------

@Enis, I'm not sure what API are yous asking for. Bigtop currently provides a way of quickly
deploying a fully distributed clusters using puppet code. You really don't want to burden
your tests with deployment logic -- hence a choice of a full fledged CM system: puppet.

We're already using that for nightly testing of the entire Hadoop stack on ~5 nodes fully
distributed clusters that we sping on-demand on EC2. Here's a job that does that:
   http://bigtop01.cloudera.org:8080/view/Test/job/DeployCluster/

And here's how a test runs looks like (bear with me while I fix a couple of things that got
broken after Bigtop's trunk migration to Hadoop 2.X):
   http://bigtop01.cloudera.org:8080/view/Test/job/SmokeCluster/
                
> A fully automated comprehensive distributed integration test for HBase
> ----------------------------------------------------------------------
>
>                 Key: HBASE-4821
>                 URL: https://issues.apache.org/jira/browse/HBASE-4821
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Mikhail Bautin
>            Assignee: Mikhail Bautin
>            Priority: Critical
>
> To properly verify that a particular version of HBase is good for production deployment
we need a better way to do real cluster testing after incremental changes. Running unit tests
is good, but we also need to deploy HBase to a cluster, run integration tests, load tests,
Thrift server tests, kill some region servers, kill the master, and produce a report. All
of this needs to happen in 20-30 minutes with minimal manual intervention. I think this way
we can combine agile development with high stability of the codebase. I am envisioning a high-level
framework written in a scripting language (e.g. Python) that would abstract external operations
such as "deploy to test cluster", "kill a particular server", "run load test A", "run load
test B" (we already have a few kinds of load tests implemented in Java, and we could write
a Thrift load test in Python). This tool should also produce intermediate output, allowing
to catch problems early and restart the test.
> No implementation has yet been done. Any ideas or suggestions are welcome.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message