[
https://issues.apache.org/jira/browse/HBASE-22086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800679#comment-16800679
]
Josh Elser commented on HBASE-22086:
------------------------------------
{quote}we rely on computing the size of the list of snapshots we list out
everytime and then re-writing it in the quota table, so it would be wise to
remove any existing snapshots entry from the quota table and have our updated
puts do the job for us.
{quote}
Good catch. Similar to another edge case like this you've fixed, I think,
Sakthi.
A tricky situation. Even after you delete a snapshot, it's not necessarily
"gone" from the filesystem yet. It would be trivial to just add some logic to
remove the size impact if we have the right MasterCP hook. But, that wouldn't
be completely accurate, and folks could delete a snapshot from HDFS by hand.
Feel free to bounce ideas. I can pull up the relevant code too.
> space quota issue: deleting snapshot doesn't update the usage of table
> ----------------------------------------------------------------------
>
> Key: HBASE-22086
> URL: https://issues.apache.org/jira/browse/HBASE-22086
> Project: HBase
> Issue Type: Bug
> Reporter: Ajeet Rai
> Assignee: Sakthi
> Priority: Minor
>
> space quota issue: deleting snapshot doesn't update the usage of table
> Steps: 1:
> set_quota TYPE => SPACE, TABLE => 'bugatti', LIMIT => '7M', POLICY =>
> NO_WRITES_COMPACTIONS
> 2: ./hbase pe --table="bugatti" --nomapred --rows=200 sequentialWrite 10
> 3: ./hbase pe --table="bugatti" --nomapred --rows=200 sequentialWrite 10
> 4: snapshot 'bugatti','bugatti_snapshot'
> 5: ./hbase pe --table="bugatti" --nomapred --rows=200 sequentialWrite 10
> 6: major_compact 'bugatti'
> 7: delete_snapshot 'bugatti_snapshot'
> now check the usage and observe that it is not getting updated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
