Anoop Sam John commented on HBASE-16803:

One thing to notice is that the visibility related admin APIs (ie. adding 
labels, assigning labels with users etc) do write to labels table by directly 
writing to labels table single region. These APIs implemented as CPEP and so 
they will come directly to region.  Other than that there is no specific reason 
to make it non splittable.  But thinking more, even if we make it splittable, 
there should not be an issue no?  The CPEP execution is such that, the client 
will find the region applicable for the rk passed and so we will hit the 
correct region. (Even if say labels table is having 2 regions)..  Said that 
same applicable for ACL table also?   Also the other jira impl as getting table 
ref from RegionEnv.  Can we use region writes/reads directly there also?

> Make hbase:acl table unsplittable
> ---------------------------------
>                 Key: HBASE-16803
>                 URL: https://issues.apache.org/jira/browse/HBASE-16803
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>         Attachments: 16803.v1.txt, 16803.v2.txt
> HBASE-16773 fixed a case where PriorityRpcServer handler threads are all 
> occupied accessing hbase:acl table.
> However, the fix relies on the fact that there is single region in hbase:acl 
> table so that the access can be local.
> As discussed at the end of HBASE-16773, we should disable split of hbase:acl 
> table as well.
> hbase:meta is normally much larger than hbase:acl table and it has only one 
> region.

This message was sent by Atlassian JIRA

Reply via email to