hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16765) New SteppingRegionSplitPolicy, avoid too aggressive spread of regions for small tables.
Date Wed, 02 Nov 2016 02:19:59 GMT

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

Hudson commented on HBASE-16765:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-1.2-JDK7 #59 (See [https://builds.apache.org/job/HBase-1.2-JDK7/59/])
HBASE-16765 New SteppingRegionSplitPolicy, avoid too aggressive spread (larsh: rev 9fcd0c8d4772847f276b9f9152a831a96973e45f)
* (add) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/SteppingSplitPolicy.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/IncreasingToUpperBoundRegionSplitPolicy.java


> 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)

Mime
View raw message