Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Thu, 18 Dec 2014 08:00:35 +0000 (UTC)
From: "Liu Junhong (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12762494.1418885192000.55281.1418889635393@Atlassian.JIRA>
In-Reply-To: <JIRA.12762494.1418885192000@Atlassian.JIRA>
References: <JIRA.12762494.1418885192000@Atlassian.JIRA>
 <JIRA.12762494.1418885192683@arcas>
Subject: [jira] [Resolved] (HBASE-12713)
 IncreasingToUpperBoundRegionSplitPolicy invalid when region count greater
 than 100
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-12713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Liu Junhong resolved HBASE-12713.
---------------------------------
    Resolution: Duplicate

Simple as HBASE-12451

> IncreasingToUpperBoundRegionSplitPolicy invalid when region count greater than 100
> ----------------------------------------------------------------------------------
>
>                 Key: HBASE-12713
>                 URL: https://issues.apache.org/jira/browse/HBASE-12713
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>    Affects Versions: 0.98.6
>            Reporter: Liu Junhong
>   Original Estimate: 4m
>  Remaining Estimate: 4m
>
> I find that the policy of region split which in IncreasingToUpperBoundRegionSplitPolicy will be invalid when the count of region is greater than 100. But sometimes 100 regions is not too much for a cluster that has 50 or more regionservers.
> So i think this policy should consider the density of the regions but not the total count of the regions.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)