[ 
https://issues.apache.org/jira/browse/HBASE-16961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989141#comment-15989141
 ] 

Andrew Purtell commented on HBASE-16961:
----------------------------------------

bq. I'm not sure if I've added short-circuits for hbase.superusers. Did you 
have some specific commands in mind WRT "system recovery actions"? 

As superuser I'd like to be able to do anything even if it (temporarily) 
violates a quota. Of course, the namespace/table for which the quota has been 
violated is now less useful for users depending on violation policy. That's 
fine. I'd clean that up as the last step of the set of administrative actions 
underway. 

bq. I could probably whip up a unit test without much hassle.

Sounds good. 

{quote}
bq.   About the optional MasterObserver for automatically deleting quotas when 
the table is deleted. Why do we not want this in general? Make it a part of 
core master, optionally disabled?

Mostly, this came in later; I think that's why I optionally enabled it. I don't 
have a good reason that it should be disable by default.
{quote}

Do we need the observer then? Make it part of core? Makes configuration 
simpler. I can see this as something you'd overlook until it is too late, then 
apply, then have to do maybe a lot of time consuming cleanup. 

> FileSystem Quotas
> -----------------
>
>                 Key: HBASE-16961
>                 URL: https://issues.apache.org/jira/browse/HBASE-16961
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>         Attachments: hbase-quota-test.sh
>
>
> Umbrella issue for tracking the filesystem utilization of HBase data, 
> defining quotas on that utilization, and enforcement when utilization exceeds 
> the limits of the quota.
> At a high level: we can define quotas on tables and namespaces. Region size 
> is computed by RegionServers and sent to the Master. The Master inspects the 
> sizes of Regions, rolling up to table and namespace sizes. Defined quotas in 
> the quota table are evaluated given the computed sizes, and, for those 
> tables/namespaces violating the quota, RegionServers are informed to take 
> some action to limit any further filesystem growth by that table/namespace.
> Discuss: 
> https://lists.apache.org/thread.html/66a4b0c3725b5cbdd61dd6111c43847adaeef7b7da5f4cd045df30ef@%3Cdev.hbase.apache.org%3E
> Design Doc: 
> http://home.apache.org/~elserj/hbase/FileSystemQuotasforApacheHBase.pdf or 
> https://docs.google.com/document/d/1VtLWDkB2tpwc_zgCNPE1ulZOeecF-YA2FYSK3TSs_bw/edit?usp=sharing



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to