hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18086) Create native client which creates load on selected cluster
Date Sat, 22 Jul 2017 00:21:00 GMT

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

Enis Soztutar commented on HBASE-18086:

bq. The tool does puts, appends, scans and gets in separate rounds.
Thanks. The logic is much more easier to follow now.  
bq. With shifted region (along with unshifted region), more than one region is involved for
the multi-get requests.
But it is still 2 regions at a time. Can we please do what I was suggesting above. You can
do something like this (assuming 10 threads): 
thread 0 reads: row_0, row_10, row_20, row_30
thread 1 reads: row_1, row_11, row_21, ... 
Other than this, looks good. 

> Create native client which creates load on selected cluster
> -----------------------------------------------------------
>                 Key: HBASE-18086
>                 URL: https://issues.apache.org/jira/browse/HBASE-18086
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>         Attachments: 18086.v11.txt, 18086.v12.txt, 18086.v14.txt, 18086.v17.txt, 18086.v18.txt,
18086.v1.txt, 18086.v3.txt, 18086.v4.txt, 18086.v5.txt, 18086.v6.txt, 18086.v7.txt, 18086.v8.txt
> This task is to create a client which uses multiple threads to conduct Puts followed
by Gets against selected cluster.
> Default is to run the tool against local cluster.
> This would give us some idea on the characteristics of native client in terms of handling
high load.

This message was sent by Atlassian JIRA

View raw message