Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 1 Nov 2016 20:22:58 +0000 (UTC)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13009664.1475609190000.148060.1478031778552@Atlassian.JIRA>
In-Reply-To: <JIRA.13009664.1475609190000@Atlassian.JIRA>
References: <JIRA.13009664.1475609190000@Atlassian.JIRA> <JIRA.13009664.1475609190621@arcas>
Subject: [jira] [Commented] (HBASE-16765) New SteppingRegionSplitPolicy,
 avoid too aggressive spread of regions for small tables.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 01 Nov 2016 20:23:00 -0000


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

Lars Hofhansl commented on HBASE-16765:
---------------------------------------

Pushed to 0.98, 1.1, 1.2, 1.3, 1.4, and 2.0 (during which I accidentally wiped history for 0.98, 1.4, and 1.1 and got heart-attach :) )

Now making it the default in 2.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
>         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)