[ https://issues.apache.org/jira/browse/HBASE-12451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14204741#comment-14204741 ]
zhangduo commented on HBASE-12451: ---------------------------------- Setting minimum split size will delay the first split operation which is good for load balancing(a new table will have only one region if not pre-split) What about reduce the boost factor(current is region_count^3) and use the total region count of this table(I do not know where is it stored but I think we can get it somewhere such as master or zookeeper) instead of the region count of this table on this server? > 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)