[
https://issues.apache.org/jira/browse/HBASE-16765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated HBASE-16765:
----------------------------------
Release Note:
Introduces a new split policy: SteppingSplitPolicy
This will use a simple step function to split a region at (by default) 2
xflushSize when no other region of the same table is seen on the region server,
or max-file-size when one or more other regions of the same table is seen.
In HBase 2.0 this is going to be the default. In previous versions it can be
configured.
> 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)
