[
https://issues.apache.org/jira/browse/HBASE-12451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205828#comment-14205828
]
Qiang Tian commented on HBASE-12451:
------------------------------------
Minimum split size is good and simple enough for me..user could have a tradeoff
between automatic tuning and customization based on knowledge of their
workload...(many times we do not want to expose too many configure parameters,
but it looks really useful in some cases:-))
based on total region count looks hard to control, e.g. if user pre-split many
regions, e.g. in
http://search-hadoop.com/m/DHED4aS08G1 with 240 regions, the size will be quite
big unless "hbase.increasing.policy.initial.size" is also configured..
> IncreasingToUpperBoundRegionSplitPolicy may cause unnecessary region splits
> in rolling update of cluster
> --------------------------------------------------------------------------------------------------------
>
> Key: HBASE-12451
> URL: https://issues.apache.org/jira/browse/HBASE-12451
> Project: HBase
> Issue Type: Bug
> Reporter: Liu Shaohui
> Assignee: Liu Shaohui
> Priority: Minor
> Fix For: 2.0.0
>
>
> Currently IncreasingToUpperBoundRegionSplitPolicy is the default region split
> policy. In this policy, split size is the number of regions that are on this
> server that all are of the same table, cubed, times 2x the region flush size.
> But when unloading regions of a regionserver in a cluster using
> region_mover.rb, the number of regions that are on this server that all are
> of the same table will decrease, and the split size will decrease too, which
> may cause the left region split in the regionsever. Region Splits also
> happens when loading regions of a regionserver in a cluster.
> A improvment may set a minimum split size in
> IncreasingToUpperBoundRegionSplitPolicy
> Suggestions are welcomed. Thanks~
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
