[
https://issues.apache.org/jira/browse/HBASE-21893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16768071#comment-16768071
]
Ajeet Rai commented on HBASE-21893:
-----------------------------------
Ideally the quota will be dropped on table drop. Have you disabled automatic
space quota deletion
>>>
Yes quota is dropped on table drop. But now I have new quota policy of 5 MB
and somehow usage is getting calculated as 8 MB so new data write is failing.
System doesn't know this. I mean how do we differentiate an earlier created
table/newly created table. We set quota on a table name.
>> OK. But from user point of view earlier created snapshot data should not be
>> used to calculate usage of new table.
> Space quota: Usage is not calculated correctly if snapshot is created on a
> table then table is deleted and created again
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-21893
> URL: https://issues.apache.org/jira/browse/HBASE-21893
> Project: HBase
> Issue Type: Bug
> Reporter: Ajeet Rai
> Priority: Minor
>
> *Steps to reproduce:*
> 1: ./hbase pe --table="bugatti" --nomapred --rows=400 sequentialWrite 10
> (will put 4 mb data)
> 2: set_quota TYPE => SPACE, TABLE => 'bugatti', LIMIT => '7M', POLICY =>
> NO_WRITES_COMPACTIONS
> 3: snapshot 'bugatti','bugatti_snapshot'
> 4: disable 'bugatti'
> 5: drop 'bugatti'
> 6: create 'bugatti','info0'
> 7: set_quota TYPE => SPACE, TABLE => 'bugatti', LIMIT => '5M', POLICY =>
> NO_WRITES_COMPACTIONS
> 8: scan 'bugatti'
> >> Observe that no data here and original snapshot size was 4 MB. but current
> >> usage is shown as 8 MB
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
