Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 11 Feb 2015 22:13:12 +0000 (UTC)
From: "Srikanth Srungarapu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12774028.1423611738000.18737.1423692792291@Atlassian.JIRA>
In-Reply-To: <JIRA.12774028.1423611738000@Atlassian.JIRA>
References: <JIRA.12774028.1423611738000@Atlassian.JIRA>
 <JIRA.12774028.1423611738762@arcas>
Subject: [jira] [Updated] (HBASE-13008) Better default for
 hbase.regionserver.regionSplitLimit parameter.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Srikanth Srungarapu updated HBASE-13008:
----------------------------------------
    Attachment: HBASE-13008_v2.patch

Patch addressing the feedback.

> Better default for hbase.regionserver.regionSplitLimit parameter.
> -----------------------------------------------------------------
>
>                 Key: HBASE-13008
>                 URL: https://issues.apache.org/jira/browse/HBASE-13008
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Srikanth Srungarapu
>            Assignee: Srikanth Srungarapu
>            Priority: Minor
>         Attachments: HBASE-13008.patch, HBASE-13008_v2.patch
>
>
> Currently, the default value for hbase.regionserver.regionSplitLimit is 2147483647. Couple of customers ran into trouble, as they ended up with too many regions(~7k) running on their region servers. Would it be possible for us to come up with better default or at least some new guard rail, which can be used for logging warnings when the number of regions are going overboard?
> Ref:
> [1] https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/CompactSplitThread.java#L101


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