[
https://issues.apache.org/jira/browse/HBASE-13008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319362#comment-14319362
]
Hudson commented on HBASE-13008:
--------------------------------
FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #807 (See
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/807/])
HBASE-13008 Better default for hbase.regionserver.regionSplitLimit parameter
(Srikanth Srungarapu) (apurtell: rev 7871c930547b078c7d63569231d646b396f40115)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/CompactSplitThread.java
* hbase-common/src/main/resources/hbase-default.xml
> 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
> Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.11
>
> 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)
