Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 1 Mar 2016 23:42:18 +0000 (UTC)
From: "Elliott Clark (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12941453.1456246708000.188365.1456875738295@Atlassian.JIRA>
In-Reply-To: <JIRA.12941453.1456246708000@Atlassian.JIRA>
References: <JIRA.12941453.1456246708000@Atlassian.JIRA>
 <JIRA.12941453.1456246708972@arcas>
Subject: [jira] [Updated] (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


     [ https://issues.apache.org/jira/browse/HBASE-15315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliott Clark updated HBASE-15315:
----------------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 1.4.0
                   1.3.0
                   2.0.0
           Status: Resolved  (was: Patch Available)

Pushed. Thanks for the contribution.

https://github.com/apache/hbase/commit/9ad13468a0cc48567b0224eba5b0a53e833a2530

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