[
https://issues.apache.org/jira/browse/HBASE-12713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252597#comment-14252597
]
zhangduo commented on HBASE-12713:
----------------------------------
{quote}
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.
{quote}
[~mopishv0], as [~lhofhansl] said, IncreasingToUpperBoundRegionSplitPolicy only
counts region locally, not globally.
If you have 100 regions and 50 regionservers, then there is only 2 regions per
regionserver(If we ignore the imbalanced scenario), right?
> 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)
