[HBASE-6201] HBase integration/system tests

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.95.2
• Fix Version/s: 0.95.0
• Component/s: test
• Assignee: Enis Soztutar
• Reporter: Enis Soztutar
• Created: 12/Jun/12 02:33
• Updated: 20/Nov/15 11:53
• Resolved: 24/Sep/13 21:21

Description

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.

Issue Links

• is cloned by: HBASE-8928 Make ChaosMonkey & LoadTest tools extensible, to allow addition of more actions and policies.
• is related to: HBASE-4821 A fully automated comprehensive distributed integration test for HBase
• relates to: HBASE-6241 HBaseCluster interface for interacting with the cluster from system tests
• relates to: BIGTOP-635 Implement a cluster-abstraction, discovery and manipulation framework for iTest
• relates to: BIGTOP-632 Release itest-common as an artifact
• relates to: HBASE-5977 Usage of modules

Sub-Tasks

• Create hbase-it module: Closed
• Enhance TestRegionRebalancing test to be a system test: Closed
• HBaseCluster interface for interacting with the cluster from system tests: Closed
• Document how to run integration tests: Closed
• Port HBaseCluster interface/tests to 0.94: Closed
• integration tests on cluster are not getting picked up from distribution: Closed
• create integration test for balancing regions and killing region servers: Closed
• on trunk, integration tests are not packaged into distribution: Closed