[jira] [Resolved] (HBASE-12451) IncreasingToUpperBoundRegionSplitPolicy may cause unnecessary region splits in rolling update of cluster

["Andrew Kyle Purtell (Jira)" <ji...@apache.org>]

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

Andrew Kyle Purtell resolved HBASE-12451.
-----------------------------------------
      Assignee:     (was: Shaohui Liu)
    Resolution: Abandoned

> 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: Shaohui Liu
>            Priority: Minor
>         Attachments: HBASE-12451-v1.diff, HBASE-12451-v2.diff
>
>
> 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
(v8.20.7#820007)