[
https://issues.apache.org/jira/browse/HBASE-22012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved HBASE-22012.
--------------------------------
Hadoop Flags: Reviewed
Resolution: Fixed
Another good bugfix here, Shardul. Well done.
> SpaceQuota DisableTableViolationPolicy will cause cycles of enable/disable
> table
> --------------------------------------------------------------------------------
>
> Key: HBASE-22012
> URL: https://issues.apache.org/jira/browse/HBASE-22012
> Project: HBase
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.2.1
> Reporter: Ajeet Rai
> Assignee: Shardul Singh
> Priority: Major
> Labels: Quota, Space
> Fix For: 3.0.0, 2.3.0, 2.1.7, 2.2.2
>
>
> Space 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
> edit (elserj): The table is automatically moved back from the violation state
> because of the code added that tried to ride over RITs. When a Region is not
> online (whether normally or abnormally), the RegionSizeReports are not sent
> from RS to Master. Eventually, enough Regions are not reported which dips
> below the acceptable threshold and we automatically move the table back to
> the "acceptable" space quota state (not in violation). We could skip this
> failsafe when we're checking for a quota that has the DisableTable violation
> policy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
