[ https://issues.apache.org/jira/browse/HBASE-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160495#comment-13160495 ]
Phabricator commented on HBASE-4908: ------------------------------------ stack has commented on the revision "[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)". @Nicolas Sure on the distinction but PE can do threaded or MR'd workloads and has a means of plugging in different loading profiles (subclass Client and then implement run). I'd think it would be better able to put up a sustained loading when loading is coming out of MR (in spite of its ugly name -- name comes from BT paper). I'm fine w/ this tool going in as is (after some cleanup). Can work then separately on unifying the two if it makes sense as a different project. REVISION DETAIL https://reviews.facebook.net/D549 > 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: Sub-task > 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