hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13375) Provide HBase superuser higher priority over other users in the RPC handling
Date Thu, 02 Apr 2015 22:07:53 GMT

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

Mikhail Antonov commented on HBASE-13375:

Hm. That'd probably simplify the things and number of checks in the implementation of PriorityFunction.
Just that looks like a bit different kinds of operations to me, in the jira you're referring
to we are elevating priority of calls lik—É reportRegionStateTransition().. not all calls
from RS to master may need to have high QoS and clog the according threadpool, and with annotations
we have the fine way to control that, right?

(for users - I think yeah, there are just 2 lists of superusers and supergroups (as returned
from VisibilityUtils, basically Pair<List<String>, List<String), and users running
RS is always included there, regardless of what's in hbase.superuser property)

> 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
> 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

View raw message