hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-16765) Improve IncreasingToUpperBoundRegionSplitPolicy
Date Tue, 04 Oct 2016 19:38:20 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15546417#comment-15546417
] 

Lars Hofhansl edited comment on HBASE-16765 at 10/4/16 7:37 PM:
----------------------------------------------------------------

In comparison, the default IncreasingToUpperBoundRegionSplitPolicy would need 5 regions per
table and server to reach the maximum split size.


was (Author: lhofhansl):
In comparison, the default IncreasingToUpperBoundRegionSplitPolicy would need 4 regions per
table and server to reach the maximum split size.

> Improve IncreasingToUpperBoundRegionSplitPolicy
> -----------------------------------------------
>
>                 Key: HBASE-16765
>                 URL: https://issues.apache.org/jira/browse/HBASE-16765
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>
> 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)

Mime
View raw message