You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ajeet Rai (JIRA)" <ji...@apache.org> on 2019/02/13 13:09:00 UTC
[jira] [Created] (HBASE-21891) New space quota policy doesn't take
effect if quota policy is changed after violation
Ajeet Rai created HBASE-21891:
---------------------------------
Summary: 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
*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)