hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "gautam (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-8928) Make ChaosMonkey & LoadTest tools extensible, to allow addition of more actions and policies.
Date Thu, 11 Jul 2013 06:49:49 GMT
gautam created HBASE-8928:

             Summary: Make ChaosMonkey & LoadTest tools extensible, to allow addition
of more actions and policies.
                 Key: HBASE-8928
                 URL: https://issues.apache.org/jira/browse/HBASE-8928
             Project: HBase
          Issue Type: Bug
          Components: test
    Affects Versions: 0.95.2
            Reporter: gautam
            Assignee: Enis Soztutar

Integration and general system tests have been discussed previously, and the conclusion is
that we need to unify how we do "release candidate" testing (HBASE-6091).

In this issue, I would like to discuss and agree on a general plan, and open subtickets for
execution so that we can carry out most of the tests in HBASE-6091 automatically. 

Initially, here is what I have in mind: 

1. Create hbase-it (or hbase-tests) containing forward port of HBASE-4454 (without any tests).
This will allow integration test to be run with
  mvn verify

2. Add ability to run all integration/system tests on a given cluster. Smt like: 
  mvn verify -Dconf=/etc/hbase/conf/
should run the test suite on the given cluster. (Right now we can launch some of the tests
(TestAcidGuarantees) from command line). Most of the system tests will be client side, and
interface with the cluster through public APIs. We need a tool on top of MiniHBaseCluster
or improve HBaseTestingUtility, so that tests can interface with the mini cluster or the actual
cluster uniformly.

3. Port candidate unit tests to the integration tests module. Some of the candidates are:

 - TestAcidGuarantees / TestAtomicOperation
 - TestRegionBalancing (HBASE-6053)
 - TestFullLogReconstruction
 - TestMasterFailover
 - TestImportExport
 - TestMultiVersions / TestKeepDeletes
 - TestFromClientSide
 - TestShell and src/test/ruby
 - TestRollingRestart
 - Test**OnCluster
 - Balancer tests

These tests should continue to be run as unit tests w/o any change in semantics. However,
given an actual cluster, they should use that, instead of spinning a mini cluster.  

4. Add more tests, especially, long running ingestion tests (goraci, BigTop's TestLoadAndVerify,
LoadTestTool), and chaos monkey style fault tests. 

All suggestions welcome. 

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