[
https://issues.apache.org/jira/browse/HBASE-25655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Baiqiang Zhao updated HBASE-25655:
----------------------------------
Description:
When we have written 100000 rows in TestTable with 10 preSplits. Then we want
to test asyncRandomRead, 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.
We can use --size and --rows in randomRead and randomSeekScan at the same time,
so that the range of reading reaches the entire data set. But asyncRandomRead,
scanRangeXX, sequentialRead and all the write still have hot spot problem.
This issue add a new option "initRows" to solve this problem.
was:
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.
> 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 asyncRandomRead, 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.
> We can use --size and --rows in randomRead and randomSeekScan at the same
> time, so that the range of reading reaches the entire data set. But
> asyncRandomRead, scanRangeXX, sequentialRead and all the write still have hot
> spot problem.
> This issue add a new option "initRows" to solve this problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
