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, 21 May 2015 06:11:01 GMT

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

Mikhail Antonov commented on HBASE-13375:
-----------------------------------------

Yeah, that makes sense I think. 

Let me rebase and post here the old patch (actually there were few improvements not related
to superusers handling in latest versions so I want to port them to old patch), and then I
can tear apart the v7 patch here  to take the code we need to change anyway and make a new
patch for the new refactoring jira (would you create one?).

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

Mime
View raw message