Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 22 Sep 2016 16:54:20 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12941453.1456246708000.639808.1474563260697@Atlassian.JIRA>
In-Reply-To: <JIRA.12941453.1456246708000@Atlassian.JIRA>
References: <JIRA.12941453.1456246708000@Atlassian.JIRA> <JIRA.12941453.1456246708972@arcas>
Subject: [jira] [Commented] (HBASE-15315) Remove always set super user call
 as high priority
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 22 Sep 2016 16:54:23 -0000


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

Andrew Purtell commented on HBASE-15315:
----------------------------------------

Please see the discussion on HBASE-16676

> Remove always set super user call as high priority
> --------------------------------------------------
>
>                 Key: HBASE-15315
>                 URL: https://issues.apache.org/jira/browse/HBASE-15315
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Yong Zhang
>            Assignee: Yong Zhang
>             Fix For: 2.0.0, 1.3.0, 1.4.0
>
>         Attachments: HBASE-15315.001.patch
>
>
> Current implementation set superuser call as ADMIN_QOS, but we have many customers use superuser to do normal table operation such as put/get data and so on. If client put much data during region assignment, RPC from HMaster may timeout because of no handle. so it is better to remove always set super user call as high priority. 


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