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

Phabricator updated HBASE-4908:
-------------------------------

    Attachment: D549.1.patch

mbautin requested code review of "[jira] [HBASE-4908] HBase cluster test tool 
(port from 0.89-fb)".
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA

  Porting one of our HBase cluster test tools (a single-process multi-threaded 
load generator and verifier) from 0.89-fb to trunk.
  I cleaned up the code a bit compared to what's in 0.89-fb, and discovered 
that it has some features that I have not tried yet (some kind of a kill test, 
and some way to run HBase as multiple processes on one machine).
  The main utility of this piece of code for us has been the HBaseClusterTest 
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a 
load test in our five-node dev cluster testing, e.g.:

  hbase org.apache.hadoop.hbase.manual.HBaseTest -load 1000000000:50:100:20 -tn 
load_test -read 1:1000000000:50:20 -zk <zk_quorum> -bloom ROWCOL -compression 
GZIP

  I will be using this code to load-test the delta encoding patch and making 
fixes, but I am submitting the patch for early feedback. I will probably try 
out its other functionality and comment on how it works.


TEST PLAN
  Run this on a dev cluster. Explore various modes of the tool (I've only tried 
the load test mode before). Probably make a unit test that runs a small local 
load test.


REVISION DETAIL
  https://reviews.facebook.net/D549

AFFECTED FILES
  src/test/java/org/apache/hadoop/hbase/manual/HBaseClusterTest.java
  src/test/java/org/apache/hadoop/hbase/manual/RestartMetaTest.java
  src/test/java/org/apache/hadoop/hbase/manual/utils/DataGenerator.java
  src/test/java/org/apache/hadoop/hbase/manual/utils/DisplayFormatUtils.java
  src/test/java/org/apache/hadoop/hbase/manual/utils/HBaseUtils.java
  src/test/java/org/apache/hadoop/hbase/manual/utils/HdfsAppender.java
  src/test/java/org/apache/hadoop/hbase/manual/utils/KillProcessesAndVerify.java
  src/test/java/org/apache/hadoop/hbase/manual/utils/MultiThreadedAction.java
  
src/test/java/org/apache/hadoop/hbase/manual/utils/MultiThreadedActionMBean.java
  src/test/java/org/apache/hadoop/hbase/manual/utils/MultiThreadedReader.java
  src/test/java/org/apache/hadoop/hbase/manual/utils/MultiThreadedWriter.java
  
src/test/java/org/apache/hadoop/hbase/manual/utils/ProcessBasedLocalHBaseCluster.java

MANAGE HERALD DIFFERENTIAL RULES
  https://reviews.facebook.net/herald/view/differential/

WHY DID I GET THIS EMAIL?
  https://reviews.facebook.net/herald/transcript/1227/

Tip: use the X-Herald-Rules header to filter Herald messages in your client.

                
> HBase cluster test tool (port from 0.89-fb)
> -------------------------------------------
>
>                 Key: HBASE-4908
>                 URL: https://issues.apache.org/jira/browse/HBASE-4908
>             Project: HBase
>          Issue Type: Test
>            Reporter: Mikhail Bautin
>            Assignee: Mikhail Bautin
>         Attachments: D549.1.patch
>
>
> Porting one of our HBase cluster test tools (a single-process multi-threaded 
> load generator and verifier) from 0.89-fb to trunk.
> I cleaned up the code a bit compared to what's in 0.89-fb, and discovered 
> that it has some features that I have not tried yet (some kind of a kill 
> test, and some way to run HBase as multiple processes on one machine).
> The main utility of this piece of code for us has been the HBaseClusterTest 
> command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a 
> load test in our five-node dev cluster testing, e.g.:
> hbase org.apache.hadoop.hbase.manual.HBaseTest -load 1000000000:50:100:20 -tn 
> load_test -read 1:1000000000:50:20 -zk <zk_quorum> -bloom ROWCOL -compression 
> GZIP
> I will be using this code to load-test the delta encoding patch and making 
> fixes, but I am submitting the patch for early feedback. I will probably try 
> out its other functionality and comment on how it works.

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