[
https://issues.apache.org/jira/browse/HBASE-13008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-13008:
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.98.11
1.1.0
1.0.1
2.0.0
Release Note: The configuration parameter
"hbase.regionserver.regionSplitLimit", the number of regions a regionserver can
open before splitting on the server is stopped to limit further region count
growth, was lowered from Integer.MAX_VALUE (2147483647) to a much more
reasonable 1000, and documented in hbase-defaults.xml.
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Pushed to 0.98+
> 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)
