[
https://issues.apache.org/jira/browse/HBASE-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176959#comment-13176959
]
Jonathan Hsieh commented on HBASE-5101:
---------------------------------------
@Andrew
I think that would be the idea. The hope is to avoid getting region servers
into trouble and to give an admin some warning when they are approaching
trouble (maybe reached some percentage of region limit).
@Ted
I've been purposely testing using a stress configuration with heavy write load
that purposely requires flushes (4 MB), splits (64MB) and compactions all the
time. Along the way region servers crash (which is fine -- fault injection is
part of this workload).
I've encountered some situations where folks don't know the distribution of
their row keys (or don't have uniform row key distributions). This could be a
useful go-between in situations where region pre-splitting with dynamic
splitting off may not be effective.
> Add a max number of regions per regionserver limit
> --------------------------------------------------
>
> Key: HBASE-5101
> URL: https://issues.apache.org/jira/browse/HBASE-5101
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 0.92.0
> Reporter: Jonathan Hsieh
>
> In a testing environment, a cluster got to a state with more than 1500
> regions per region server, and essentially became stuck and unavailable. We
> could add a limit to the number of regions that a region server can serve to
> prevent this from happening. This looks like it could be implemented in the
> core or as a coprocessor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
