hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mubarak Seyed (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4917) CRUD Verify Utility
Date Wed, 25 Jan 2012 19:53:53 GMT

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

Mubarak Seyed commented on HBASE-4917:


How different this LoadTest tool from PerformanceEvaluation 

hbase org.apache.hadoop.hbase.PerformanceEvaluation
Usage: java org.apache.hadoop.hbase.PerformanceEvaluation \
  [--miniCluster] [--nomapred] [--rows=ROWS] <command> <nclients>

I believe LoadTester.java generates load for multiple column families (provided there is an
external properties file to define the CFs and their definition, read/write threads, regions/server)
where as PerformanceEvaluation uses only one CF (TestTable:info).

How does LoadTester differ from YCSB, i believe YCSB supports only one CF as well.

I think LoadTester can be used for burn-in test (when we provision a new cluster and sniff
the cluster). 

If no one is working on this issue, i can help porting loadtest to src/test/java/org/apache/hadoop/hbase/loadtest.


> CRUD Verify Utility
> -------------------
>                 Key: HBASE-4917
>                 URL: https://issues.apache.org/jira/browse/HBASE-4917
>             Project: HBase
>          Issue Type: Sub-task
>          Components: client, regionserver
>            Reporter: Nicolas Spiegelberg
>             Fix For: 0.94.0
> Add a verify utility to run basic CRUD tests against hbase in various common use cases.
 This is great for sanity checking a cluster setup because it can be run as a one line shell
command with no required params.  Multiple column families for different use-cases can be
tested together.  Currently provided use-cases are 'action log', 'snapshot' and 'search'.
The interface is developed such that it can be easily extended to cover more use-cases.

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


View raw message