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

WangYuan commented on HBASE-17983:
----------------------------------

Sorry, my description is not very accurate. In fact, I hope to keep the 
performance of HBase put and get relatively stable.Create a new table then 
region (EG:100 partition) increase, then bulkload .So data will increase and 
meanwhile client's concurrent will also increase . You said that the reduction 
of handle number, I think it may block the requests, because the length of the 
RPC queue is the default number of handle multiplied by 10, so that the queue 
length becomes shorter.

If we can limit the number of regions in each regionserver in a reasonable 
range, so that even if the number of concurrent become larger and  regions 
become more and more, I only need to increase the size of the regionserver 
clusters by a rule:
hbase.client.region.averageload.numbers .
So whether  concurrent or regions increases, the performance can remain stable.

> control region numbers when create table to improve performance
> ---------------------------------------------------------------
>
>                 Key: HBASE-17983
>                 URL: https://issues.apache.org/jira/browse/HBASE-17983
>             Project: HBase
>          Issue Type: Improvement
>          Components: Admin, Client
>    Affects Versions: 2.0.0
>            Reporter: WangYuan
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: 
> HBASE-17983-control-region-numbers-when-create-table.patch
>
>
> I found that with the increasing number of regions in every RegionServer , 
> HBase read and write performance decreased, and failed to achieve the desired 
> performance. Therefore, we hope to control the number of regions in every 
> RegionServer , and add the judgment before creating tables.
> I can set up a region parameter in hbase-default.xml, 
> hbase.client.region.averageload.numbers, when the client builds a table that 
> exceeds the value of this parameter, throws an exception.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to