[
https://issues.apache.org/jira/browse/HBASE-16765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615823#comment-15615823
]
Lars Hofhansl commented on HBASE-16765:
---------------------------------------
Lost sight of this.
I think this should be the default. Can only be in a major release (or perhaps
in a minor release), the risk is that after running with this for a while and
then rolling back the upgrade one might run into a split-storm, as the old
policy will split more aggressively. Not sure if that is enough to not put it
into the next minor release.
Lemme commit this, after explaining more in the comments.
> Improve IncreasingToUpperBoundRegionSplitPolicy
> -----------------------------------------------
>
> Key: HBASE-16765
> URL: https://issues.apache.org/jira/browse/HBASE-16765
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Attachments: 16765-0.98.txt
>
>
> We just did some experiments on some larger clusters and found that while
> using IncreasingToUpperBoundRegionSplitPolicy generally works well and is
> very convenient, it does tend to produce too many regions.
> Since the logic is - by design - local, checking the number of regions of the
> table in question on the local server only, we end with more regions then
> necessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
