[
https://issues.apache.org/jira/browse/HBASE-13375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14488251#comment-14488251
]
Josh Elser commented on HBASE-13375:
------------------------------------
bq. Now we're checking that rpc is access to system table (qos 200) after we
check annotations (which means, manually setting annotation on certain rpc
overrides access to system table?).
Good point. I didn't read down far enough to catch that the first time around.
Reading it fully, I agree with your assessment.
bq. And beyond that we might want to specify in what order we check the rules
I can easily see some kind of "formal" rule-based approach to this (rather then
how the conditionals fall), but I'm not quite certain it's necessary at this
point. Future work could include per-user/group priority delegation, but, aside
from that, I'm failing to come up with anything more that could be added which
would create more complexity that a more elegant priority-function would
ultimately simplify.
> 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.0
>
> Attachments: HBASE-13375-v0.patch, HBASE-13375-v1.patch,
> HBASE-13375-v1.patch, HBASE-13375-v1.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)
