[
https://issues.apache.org/jira/browse/HBASE-22013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16788020#comment-16788020
]
Josh Elser commented on HBASE-22013:
------------------------------------
What version(s) of HBase?
{quote}bq. It looks like File system utilization core is sending data of 100
reasons but not the size of region replicas.
{quote}
This is as expected. Region replicas do not take up any more space on the
filesystem.
{quote}But in quota observer chore, it is considering total region(actual
regions+ replica reasons)
{quote}
Please provide the information that you observed which lead you to this
conclusion. The QuotaObserverChore is using hte data that was reported by the
FileSystemUtilizationChore. Thus, your analysis doesn't make sense to me.
> Space Quota: Space Quota Issue: If a table is created with region replica
> then quota calculation is not happening
> -----------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-22013
> URL: https://issues.apache.org/jira/browse/HBASE-22013
> Project: HBase
> Issue Type: Bug
> Reporter: Ajeet Rai
> Priority: Major
>
> Space Quota: Space Quota Issue: If a table is created with region replica
> then quota calculation is not happening
> Steps:
> 1: Create a table with 100 regions with region replica 3
> 2: Observe that 'hbase:quota' table doesn't have entry of usage for this
> table So In UI only policy Limit and Policy is shown but not Usage and State.
> Reason:
> It looks like File system utilization core is sending data of 100 reasons
> but not the size of region replicas.
> But in quota observer chore, it is considering total region(actual regions+
> replica reasons)
> So the ratio of reported regions is less then configured
> percentRegionsReportedThreshold.
> SO quota calculation is not happening
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
