You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Baiqiang Zhao (Jira)" <ji...@apache.org> on 2021/03/10 08:20:00 UTC

[jira] [Comment Edited] (HBASE-25655) Add a new option in PE to indicate the current number of rows in the test table

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

Baiqiang Zhao edited comment on HBASE-25655 at 3/10/21, 8:19 AM:
-----------------------------------------------------------------

Thanks [~anoop.hbase]. Yes, use --size can not hot spot one or few regions for randomRead and randomSeekScan. My example may be a bit special. But what about asyncRandomRead, scanRangeXX etc. 


was (Author: deanz):
Thanks [~anoop.hbase]. Yes, use --size can not hot spot one or few regions for randomRead and randomSeekScan. My example may be a bit special. But what about asyncRandomRead, append, checkAndPut, scanRangeXX etc. 

> Add a new option in PE to indicate the current number of rows in the test table
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-25655
>                 URL: https://issues.apache.org/jira/browse/HBASE-25655
>             Project: HBase
>          Issue Type: Improvement
>          Components: PE
>            Reporter: Baiqiang Zhao
>            Assignee: Baiqiang Zhao
>            Priority: Major
>
> When we have written 100000 rows in TestTable with 10 preSplits. Then we want to test randomRead with 10 threads, per thread read 1000 rows. But the range of all read keys is in [0, 10000], all in the first region. It may cause hotspot problem, and the result is not accurate.
> This issue add a new option "initRows" to  solve this problem.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)