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

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

Thank you.
I read HBASE-8410, It's a good issue,but I understand issue's point of view is 
different. 
One is the RegionServer level to control average Region number, one is the 
overall control of the NameSpace level.

For example: in our cluster RegionServer average load of Region increased from 
200 then 500 then 1000, single read and write performance will increase from 
5ms  then 10ms   then 100ms. I don't want to go down.

But  HBASE-8410 should not explain the relationship between RegionServer and 
Region numbers in it .
Because the number of RegionServer nodes can be increased (When data increases 
or table numbers increases), I want to control the average number of region 
load ,rather than total table numbers or region numbers.



> 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