hbase-issues mailing list archives

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

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

Srikanth Srungarapu commented on HBASE-13008:
---------------------------------------------

In the configuration guidelines, we're [recommending|http://hbase.apache.org/book.html#ops.capacity.regions]
20-200 regions. So, 1000 seems to be a very sensible upper limit. Will post a patch soon.

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