[ 
https://issues.apache.org/jira/browse/HBASE-22342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938275#comment-16938275
 ] 

Shardul Singh commented on HBASE-22342:
---------------------------------------

Hi [~elserj] and [~jatsakthi], I need your expertise in this one.Problem is 
quotaUsage is shows double for 10 minutes because of the conf 
"hbase.master.quotas.region.report.retention.millis" default value.  

 So the solution which I came up is as follows:

1. I was thinking that we should not remove the region report if it is 
split/merge from regionSize cache as we did in HBASE-22012.

2. Catalog Janitor can take up the responisbility of removing the region report 
from the cache while deleting references for the merge/split region.

3. During master startup we can add a logic for Calculating the size of region 
if it's a splitParent or mergeParent and put it in the cache if the region 
state still exists in the cluster.


> space quota usage is calculated almost double then actual usage in case of 
> Split /Merge of region
> -------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-22342
>                 URL: https://issues.apache.org/jira/browse/HBASE-22342
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>            Reporter: Ajeet Rai
>            Assignee: Shardul Singh
>            Priority: Minor
>              Labels: quota, space
>
> space quota usage is calculated double for some time because it is 
> considering the usage of the parent region report received earlier. This is 
> normal behaviour because *hbase.master.quotas.region.report.retention.millis* 
> is set as 10 minutes.It's not calculating the usage from the store files, 
> it's taking the usage from the earlier report send to the master by the 
> parent region server till 10 minutes.
> So after 10 minutes, it stops considering the earlier region report and quota 
> is not violated



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to