Improvements in tests
---------------------

                 Key: HBASE-4703
                 URL: https://issues.apache.org/jira/browse/HBASE-4703
             Project: HBase
          Issue Type: Improvement
          Components: test
    Affects Versions: 0.92.0
         Environment: all
            Reporter: nkeywal
            Assignee: nkeywal
            Priority: Minor


Global:
 - when possible, make the test using the default cluster configuration for the 
number of region (1 instead of 2 or 3). This allows a faster stop/start, and is 
a step toward a shared cluster configuration.
 - 'sleep': lower or remove the sleep based synchronisation in the tests (in 
HBaseTestingUtility, TestGlobalMemStoreSize, TestAdmin, 
TestCoprocessorEndpoint, TestHFileOutputFormat, TestLruBlockCache, 
TestServerCustomProtocol, TestReplicationSink)
  - tmp dir management: to allow multiple tests using dir to run on the same 
machine without conflicting, the tmp dir is set once per JVM. This should fix 
HBASE-3672 as well, because the map reduce cluster is configured to use the 
hadoop tmp dir
  - Optimize 'put' by setting setWriteToWAL to false, when the 'put' is big or 
in a loop. Not done for tests that rely on the WAL.
 
Local issues:
- TestTableInputFormatScan fully deletes the hadoop.tmp.dir directory on 
tearDown, that makes it impossible to use in // with another test using this 
directory
- TestIdLock logs too much (9000 lines per seconds). Test time lowered to 15 
seconds to make it a part of the small subset
- TestMemoryBoundedLogMessageBuffer useless System.out.println
- io.hfile.TestReseekTo useless System.out.println
- TestTableInputFormat does not shutdown the cluster
- testGlobalMemStore does not shutdown the cluster
- rest.client.TestRemoteAdmin: simplified, does not use local admin, single 
test instead of two.
- HBaseTestingUtility#ensureSomeRegionServersAvailable starts only one server, 
should start the number of missing server instead.
- TestMergeTool should starts/stops the dfs cluster with HBaseTestingUtility

--
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

        

Reply via email to