Return-Path: 
 <issues-return-196740-apmail-hbase-issues-archive=hbase.apache.org@hbase.apache.org>
X-Original-To: apmail-hbase-issues-archive@www.apache.org
Delivered-To: apmail-hbase-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 300191754E
	for <apmail-hbase-issues-archive@www.apache.org>;
 Wed, 20 May 2015 11:39:01 +0000 (UTC)
Received: (qmail 70937 invoked by uid 500); 20 May 2015 11:39:01 -0000
Delivered-To: apmail-hbase-issues-archive@hbase.apache.org
Received: (qmail 70908 invoked by uid 500); 20 May 2015 11:39:01 -0000
Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@hbase.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@hbase.apache.org>
List-Post: <mailto:issues@hbase.apache.org>
List-Id: <issues.hbase.apache.org>
Delivered-To: mailing list issues@hbase.apache.org
Received: (qmail 70896 invoked by uid 99); 20 May 2015 11:39:00 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 May 2015 11:39:00 +0000
Date: Wed, 20 May 2015 11:39:00 +0000 (UTC)
From: "Anoop Sam John (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12787254.1427865300000.167989.1432121940886@Atlassian.JIRA>
In-Reply-To: <JIRA.12787254.1427865300000@Atlassian.JIRA>
References: <JIRA.12787254.1427865300000@Atlassian.JIRA>
 <JIRA.12787254.1427865300272@arcas>
Subject: [jira] [Commented] (HBASE-13375) Provide HBase superuser higher
 priority over other users in the RPC handling
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

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

This is what new class I thought
{code}
class Authentication** { // Not getting a name

//singleton instance
private List<String> superUsers, superGroups;

public static initialize(Configuration){
 // initialize super user/group lists here
}

public static getInstance() {
  // throw RTE when called before initialize
}

public boolean isSuperUser(User){

}

//Group related utils.
public static isGroup()
public static getGroupName()

}
{code}


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