[
https://issues.apache.org/jira/browse/HBASE-22142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shardul Singh updated HBASE-22142:
----------------------------------
Description:
steps to follow:
1.create a quota at namespace level
2.create 2 tables t1 and t2 inside namespace and write data.
3.write 5 mb of data each in both t1 and t2.
4. drop t1.
5. data usage for t2 will be shown 10 mb for 10 minutes.
If table is dropped inside namespace, data size usage is still shown for 10
minutes because of the configuration
"hbase.master.quotas.region.report.retention.millis". This conf maintains the
region report in cache(regionSizes) and old entry is used for 10 minutes. We
can remove the entry from cache during the drop command as part of MasterCP
hook only, so that correct usage is show instantaneously after the drop command.
was:
steps to follow:
1.create a quota at namespace level
2.create 2 tables t1 and t2 inside namespace and write data.
3.write 5 mb of data each in both t1 and t2.
4. drop t1.
5. data usage for t2 will be shown 10 mb for 10 minutes.
If table is dropped inside namespace, data size usage is still shown for 10
minutes because of the configuration
"hbase.master.quotas.region.report.retention.millis". This conf maintains the
region report in cache(regionSizes) and old entry is used for 10 minutes. We
can remove the entry during the drop command only, so that correct usage is
show instantaneously after the drop command.
> Space quota: If table inside namespace having space quota is dropped, data
> size usage is still considered for the drop table.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-22142
> URL: https://issues.apache.org/jira/browse/HBASE-22142
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.1.1
> Reporter: Shardul Singh
> Priority: Minor
>
> steps to follow:
> 1.create a quota at namespace level
> 2.create 2 tables t1 and t2 inside namespace and write data.
> 3.write 5 mb of data each in both t1 and t2.
> 4. drop t1.
> 5. data usage for t2 will be shown 10 mb for 10 minutes.
> If table is dropped inside namespace, data size usage is still shown for 10
> minutes because of the configuration
> "hbase.master.quotas.region.report.retention.millis". This conf maintains the
> region report in cache(regionSizes) and old entry is used for 10 minutes. We
> can remove the entry from cache during the drop command as part of MasterCP
> hook only, so that correct usage is show instantaneously after the drop
> command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
