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

Francis Liu commented on HBASE-8015:
------------------------------------

{quote}
How do you plan to enforce this? WAL's completely bypass the quota, and if a 
ns's quota fills up, it cannot flush, and compact, which will affect all of the 
other namespaces. I am not against the idea of having a parent namespace dir 
for tables, but just wondering whether this is really feasible. 
{quote}
Maybe we should have WALs per namespace per server :-). If we want other 
namespace based features (ie replication) going this route makes sense?

Internally we plan to do it using regionserver groups (one namespace per 
group). Since we don't want our tenants contending for other resources as well 
(disk, mem, cpu, etc).

{quote}
Can't we enforce quotas at the HBase level, since we are doing ACL's at the 
application layer for the same reasons.
{quote}
It'd be good if we can leverage hdfs quota since it's already there and has 
worked well (at least for us). That's also less complexity for us, then we can 
focus on adding HBase specific Quota (ie regions, tables, etc).



                
> Support for Namespaces
> ----------------------
>
>                 Key: HBASE-8015
>                 URL: https://issues.apache.org/jira/browse/HBASE-8015
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Francis Liu
>            Assignee: Francis Liu
>         Attachments: HBASE-8015_draft_94.patch, NamespaceDesign.pdf
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to