hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13008) Better default for hbase.regionserver.regionSplitLimit parameter.
Date Wed, 11 Feb 2015 22:16:12 GMT

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

Andrew Purtell commented on HBASE-13008:
----------------------------------------

+1

Will commit shortly to 0.98+ unless objection.

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

Mime
View raw message