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:25:00 UTC
[jira] [Updated] (HBASE-21892) If a new table is created inside a
namespace then NS quota violation is not working for first time
[ https://issues.apache.org/jira/browse/HBASE-21892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ajeet Rai updated HBASE-21892:
------------------------------
Description:
If a new table is created inside a namespace then NS quota violation is not working for first time.
Steps to reproduce:
1: Set a space quota at NameSpace level
set_quota TYPE => SPACE, NAMESPACE => 'game', LIMIT => '10M', POLICY => NO_WRITES
2: create a table and add insert data such that NS quota is violated
create_namespace 'game'
./hbase pe --table="game:nfs" --nomapred --rows=120 sequentialWrite 10
3: Try to load data in table again and observe that quota is applicable
4: Now create another table under same NS and put some data
create_namespace 'game'
./hbase pe --table="game:nfs2" --nomapred --rows=120 sequentialWrite 10
5: Observe that data is inserted in new table which should not happen due to namespace quota is already violated
was:
If a new table is created inside a namespace then NS quota violation is not working for first time.
Steps to reproduce:
1: Set a space quota at NameSpace level
2: create a table and add insert data such that NS quota is violated
3: Try to load data in table again and observe that quota is applicable
4: Now create another table under same NS and put some data
5: Observe that data is inserted in new table which should not happen due to namespace quota is already violated
> If a new table is created inside a namespace then NS quota violation is not working for first time
> --------------------------------------------------------------------------------------------------
>
> Key: HBASE-21892
> URL: https://issues.apache.org/jira/browse/HBASE-21892
> Project: HBase
> Issue Type: Bug
> Reporter: Ajeet Rai
> Priority: Minor
>
> If a new table is created inside a namespace then NS quota violation is not working for first time.
> Steps to reproduce:
> 1: Set a space quota at NameSpace level
> set_quota TYPE => SPACE, NAMESPACE => 'game', LIMIT => '10M', POLICY => NO_WRITES
> 2: create a table and add insert data such that NS quota is violated
> create_namespace 'game'
> ./hbase pe --table="game:nfs" --nomapred --rows=120 sequentialWrite 10
> 3: Try to load data in table again and observe that quota is applicable
> 4: Now create another table under same NS and put some data
> create_namespace 'game'
> ./hbase pe --table="game:nfs2" --nomapred --rows=120 sequentialWrite 10
> 5: Observe that data is inserted in new table which should not happen due to namespace quota is already violated
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)