[
https://issues.apache.org/jira/browse/HBASE-13964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605294#comment-14605294
]
Mikhail Antonov commented on HBASE-13964:
-----------------------------------------
While thinking more on that, I 'm back to name vs space based quotas (maybe we
should move this to dev lists though?)
Like in HDFS there's name (# of inodes) and space (# of bytes) quotas. Bytes
are resources in terms of underlying storage, inodes are resources in terms of
space in fsimage (I assume, please correct me if I'm wrong). In HBase we have
quotas on # of tables and regions, which are resources from assignment manager
throughput viewpoint, and indirect limit of storage space used (can't eat up
more than # of regions X max region size).
On the other hand, we could just set quota in bytes directly, and allow any
split/merges to happen, since it can be considered that user is limited in the
amount of data he/she could store in HBase, but the layout of this data is
(optionally) optimized and controlled by HBase itself, so we may not want
direct limit of # of regions.
[[email protected]], [~ndimiduk] - thoughts?
> 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)
