Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 10 Feb 2016 19:41:18 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12938272.1455129692000.19381.1455133278093@Atlassian.JIRA>
In-Reply-To: <JIRA.12938272.1455129692000@Atlassian.JIRA>
References: <JIRA.12938272.1455129692000@Atlassian.JIRA>
 <JIRA.12938272.1455129692186@arcas>
Subject: [jira] [Updated] (HBASE-15249) Provide lower bound on number of
 regions in region normalizer for pre-split tables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ted Yu updated HBASE-15249:
---------------------------
    Attachment: HBASE-15249.v1.txt

Draft patch

> Provide lower bound on number of regions in region normalizer for pre-split tables
> ----------------------------------------------------------------------------------
>
>                 Key: HBASE-15249
>                 URL: https://issues.apache.org/jira/browse/HBASE-15249
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>         Attachments: HBASE-15249.v1.txt
>
>
> AMS (Ambari Metrics System) developer found the following scenario:
> Metrics table was pre-split with many regions on large cluster.
> After some time, AMS stopped working because region normalizer merged the regions into few big regions which were not able to serve high read / write load.
> We should consider setting reasonable lower bound on region count.
> If the table is pre-split, we can use initial region count as the lower bound.


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