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

Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2014/12/23 05:28:13 UTC

[jira] [Issue Comment Deleted] (HBASE-12713) IncreasingToUpperBoundRegionSplitPolicy invalid when region count greater than 100

     [ https://issues.apache.org/jira/browse/HBASE-12713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Hofhansl updated HBASE-12713:
----------------------------------
    Comment: was deleted

(was: Yes，but sometimes i should disable the load balancer. This policy is not applicable this case?)

> IncreasingToUpperBoundRegionSplitPolicy invalid when region count greater than 100
> ----------------------------------------------------------------------------------
>
>                 Key: HBASE-12713
>                 URL: https://issues.apache.org/jira/browse/HBASE-12713
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>    Affects Versions: 0.98.6
>            Reporter: Liu Junhong
>   Original Estimate: 4m
>  Remaining Estimate: 4m
>
> I find that the policy of region split which in IncreasingToUpperBoundRegionSplitPolicy will be use the value of "maxfilesize" when the count of region is greater than 100. But sometimes 100 regions is not too much for a cluster that has 50 or more regionservers.
> So i think this policy should consider the density of the regions but not the total count of the regions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)