[
https://issues.apache.org/jira/browse/HBASE-13964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605282#comment-14605282
]
Mikhail Antonov commented on HBASE-13964:
-----------------------------------------
I think that we don't really have justification for not allowing merging of
regions in quota-enabled namespaces, as merge never results in namespace quota
violation, so this is a useful improvement to have. And merging of bunch of
small regions was mentioned as a valid usecase before.
[[email protected]] in earlier version of patch where we introduced region
normalization I had the enum with {merge,split} operation types, but then it
was removed after reviews as perception was we don't really need this.. I'm
thinking we may not need this enum, as we already pass table name in region
normalizer, and there's MasterServices field there. So we should be able to
call MS#getMasterQuotaManager() inside normalizer and find out if there're
quotas on the namespace the region belongs to, then we don't issue split plan
if that's the case. What do you think (maybe I'm missing something)? Also with
this approach I assume we would pass all enabled tables to normalizer?
Hm. I'm not sure why do we need to distinguish between split/merge requests
issues by normalizer vs. issued by end user?
> Skip region normalization for tables under namespace quota
> ----------------------------------------------------------
>
> Key: HBASE-13964
> URL: https://issues.apache.org/jira/browse/HBASE-13964
> Project: HBase
> Issue Type: Task
> Components: Balancer, Usability
> Reporter: Mikhail Antonov
> Assignee: Ted Yu
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: 13964-branch-1-v2.txt, 13964-branch-1-v3.txt,
> 13964-v1.txt
>
>
> As [[email protected]] pointed out in HBASE-13103, we need to discuss how to
> normalize regions of tables under namespace control. What was proposed is to
> disable normalization of such tables.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
