[
https://issues.apache.org/jira/browse/HBASE-21891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nihal Jain resolved HBASE-21891.
--------------------------------
Resolution: Duplicate
Based on [~a00408367]
[testing|https://issues.apache.org/jira/browse/HBASE-20662?focusedCommentId=16785275&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16785275],
resolving this as duplicate. This issue is fixed by HBASE-20662.
> New space quota policy doesn't take effect if quota policy is changed after
> violation
> -------------------------------------------------------------------------------------
>
> Key: HBASE-21891
> URL: https://issues.apache.org/jira/browse/HBASE-21891
> Project: HBase
> Issue Type: Bug
> Reporter: Ajeet Rai
> Priority: Minor
>
> *Steps to reproduce*
> 1: set_quota TYPE => SPACE, TABLE => 'test25', LIMIT => '2M', POLICY =>
> NO_WRITES
> 2: ./hbase pe --table="test25" --nomapred --rows=300 sequentialWrite 10
> 3: Observe that after some time data usage is 3 mb and policy is in violation
> 4: now try to insert some data again in the table and observe that operation
> fails due to NoWritesViolationPolicyEnforcement
> 5: Now change the quota policy
> set_quota TYPE => SPACE, TABLE => 'test25', LIMIT => '2M', POLICY =>
> NO_WRITES_COMPACTIONS
> 6: Now again try to insert data once new policy takes effect
> 7: Observe that still operation fails but because of old policy and not new
> policy.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
