[
https://issues.apache.org/jira/browse/HBASE-15044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073766#comment-15073766
]
Mikhail Antonov commented on HBASE-15044:
-----------------------------------------
Without synchronization if we just check for current quota and then proceed, we
could end up exceeding quota, as we are not the only endpoint splitting regions
(there are shell commands, REST, split policies etc)? We need to grab some kind
of lock on namespace still?
> Region normalization should be allowed when underlying namespace has quota
> --------------------------------------------------------------------------
>
> Key: HBASE-15044
> URL: https://issues.apache.org/jira/browse/HBASE-15044
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: Ted Yu
> Attachments: 15044-v1.txt, 15044-v2.txt
>
>
> Currently when namespace has quota, HMaster#normalizeRegions() skips the
> tables in the namespace.
> However, performing region merge(s) wouldn't violate quota constraint.
> For region split, NamespaceAuditor#checkQuotaToSplitRegion() can be called to
> check whether quota is about to be exceeded. If not, region split plan can
> still be executed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
