You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2016/11/01 21:31:58 UTC
[jira] [Resolved] (HBASE-16765) New SteppingRegionSplitPolicy,
avoid too aggressive spread of regions for small tables.
[ https://issues.apache.org/jira/browse/HBASE-16765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl resolved HBASE-16765.
-----------------------------------
Resolution: Fixed
Assignee: Lars Hofhansl
Fix Version/s: 1.1.8
0.98.24
1.2.4
1.4.0
1.3.0
2.0.0
> New SteppingRegionSplitPolicy, avoid too aggressive spread of regions for small tables.
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-16765
> URL: https://issues.apache.org/jira/browse/HBASE-16765
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.4, 0.98.24, 1.1.8
>
> 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)