[jira] [Resolved] (HBASE-22014) Space Quota: If some reasons are offline then quota usage calculation is not happening.

["Josh Elser (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-22014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser resolved HBASE-22014.
--------------------------------
    Resolution: Invalid

Invalid – this works as designed.

The QuotaObserverChore will not act unless it receives region size reports from at least {{hbase.master.quotas.observer.report.percent}} of the Regions for a table. This prevents RITs from moving a quota into violation.

A submission to add a sub-section to [https://hbase.apache.org/book.html#space-quotas] that covers this detail would be helpful.

> Space Quota: If some reasons are offline then quota usage calculation is not happening.
> ---------------------------------------------------------------------------------------
>
>                 Key: HBASE-22014
>                 URL: https://issues.apache.org/jira/browse/HBASE-22014
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ajeet Rai
>            Priority: Minor
>
> Space Quota: If some reasons are offline then quota usage calculation is not happening.
> Steps:
> Scenario1:
> 1: create 'testmultireason','info0',SPLITS => ['100','200','300','400','500','600','700','800','900','1000']
> 2: unassign '3f356ccac99fba4e12741a57f79a18a7' // close one of the region
> 3: set_quota TYPE => SPACE, TABLE => 'testmultireason', LIMIT => '3M', POLICY => NO_INSERTS
> 4: put some data
> 5: observe that after some time data usage and state is also shown but usage is 0 only even if data has crossed quota limit
> Scenario2:
> 1: set_quota TYPE => SPACE, TABLE => 'testmultireason2', LIMIT => '3M', POLICY => NO_INSERTS
> 2: create 'testmultireason2','info0',SPLITS => ['100','200','300','400','500','600','700','800','900','1000']
> 3: unassign '3b6e28e0060596e35814673ef4941d4c' //close one of the region
> 4: put 4 mb data and observe that policy is in violation
> 5: Observe after some time policy is changed from violation to In Observance



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)