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

Anoop Sam John commented on HBASE-13375:
----------------------------------------

My only concerns were util methods added to User class.  These are group 
related stuff. 
getGroupName(String aclKey) 
isGroupPrincipal(String name)
I am -0 for that.

Or can we move them to a new AuthenticationUtil or so? If this new class can be 
like a non util thing (some better name we need), we can even move the super 
user check also there. (isSuperUser(User)).   We can make this singleton and 
instantiate once passing the configuration.  That way we can even keep the User 
class untouched and no static variables( List of super users) addition..   What 
all think abt this?

> Provide HBase superuser higher priority over other users in the RPC handling
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-13375
>                 URL: https://issues.apache.org/jira/browse/HBASE-13375
>             Project: HBase
>          Issue Type: Improvement
>          Components: rpc
>            Reporter: Devaraj Das
>            Assignee: Mikhail Antonov
>             Fix For: 1.1.1
>
>         Attachments: HBASE-13375-v0.patch, HBASE-13375-v1.patch, 
> HBASE-13375-v1.patch, HBASE-13375-v1.patch, HBASE-13375-v2.patch, 
> HBASE-13375-v3.patch, HBASE-13375-v4.patch, HBASE-13375-v5.patch, 
> HBASE-13375-v6.patch, HBASE-13375-v7.patch
>
>
> HBASE-13351 annotates Master RPCs so that RegionServer RPCs are treated with 
> a higher priority compared to user RPCs (and they are handled by a separate 
> set of handlers, etc.). It may be good to stretch this to users too - hbase 
> superuser (configured via hbase.superuser) gets higher priority over other 
> users in the RPC handling. That way the superuser can always perform 
> administrative operations on the cluster even if all the normal priority 
> handlers are occupied (for example, we had a situation where all the master's 
> handlers were tied up with many simultaneous createTable RPC calls from 
> multiple users and the master wasn't able to perform any operations initiated 
> by the admin). (Discussed this some with [~enis] and [~elserj]).
> Does this make sense to others?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to