[
https://issues.apache.org/jira/browse/HBASE-20613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484380#comment-16484380
]
Biju Nair edited comment on HBASE-20613 at 5/22/18 7:39 PM:
------------------------------------------------------------
Also this leaves {{regions}} in {{SPLITTING}} state. This is noticed by running
{{PE }} {{sequentialWrite}} and the last region (which meets the region limit)
that grows in size is left in {{splitting}} state.
was (Author: gsbiju):
Also this leaves {{regions}} in {{SPLITTING}} state. This is noticed by running
{{PE }} {{sequentialWrite}} and the last region (which meets the region limit)
which grows in size is left in {{splitting}} state.
> Limiting region count results in large size regions
> ---------------------------------------------------
>
> Key: HBASE-20613
> URL: https://issues.apache.org/jira/browse/HBASE-20613
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Reporter: Biju Nair
> Priority: Major
>
> Restricting the total number of regions in a {{namespace}}, results in large
> regions. Not sure whether it is by design i.e. restrict the number of region
> even if the region sizes grow large. Steps to recreate.
> - Create a namespace with restriction on the number of regions
> {noformat}
> create_namespace 'ns2',
> {'hbase.namespace.quota.maxtables'=>'2','hbase.namespace.quota.maxregions'=>'5'}{noformat}
> - Create a table and run {{PE}} to load data. The table can be created with
> a small _hbase_._hregion_._max_._filesize_
> - After 5 regions, the region size grows beyond
> _hbase_._hregion_._max_._filesize._ Since the region count restriction
> prevents splits, the region size grows
> Will it be better to gracefully error out when regions can't be split?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
