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

Hudson commented on HBASE-15315:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-1.2-JDK8 #27 (See 
[https://builds.apache.org/job/HBase-1.2-JDK8/27/])
HBASE-15315 Remove always set super user call as high priority (Yong (apurtell: 
rev 32a7f2c4b80b4d5f05889f1669aa1538450b6d7a)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestPriorityRpc.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/AnnotationReadingPriorityFunction.java


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

Reply via email to