[
https://issues.apache.org/jira/browse/HBASE-22012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793340#comment-16793340
]
Ajeet Rai commented on HBASE-22012:
-----------------------------------
Currently there is issue if table is disabled, it is not getting enabled if any
change in limit or policy etc. Please refer HBASE-20662 for this behaviour.
Patch is available for this issue and it works fine normally.
But in case of table is disabled, regions are closed and hence region size is
not getting calculated.
Now since region size is not available, as per behaviour, quota policy state
will change to 'in observant' and table will be enabled again.
Now since table is already crossed usage limit, it will be disabled again.
So this cycle of table getting disabled and enabled will continue .
> Space Quota: Policy state is getting changed from disable to Observance after
> sometime automatically.
> -----------------------------------------------------------------------------------------------------
>
> Key: HBASE-22012
> URL: https://issues.apache.org/jira/browse/HBASE-22012
> Project: HBase
> Issue Type: Bug
> Reporter: Ajeet Rai
> Priority: Minor
>
> pace Quota: Policy state is getting changed from disable to Observance after
> sometime automatically.
> Steps:
> 1: Create a table with space quota policy as Disable
> 2: Put some data so that table state is in space quota violation
> 3: So observe that table state is in violation
> 4: Now wait for some time
> 5: Observe that after some time table state is changing to to Observance
> however table is still disabled
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
