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

Hudson commented on HBASE-14322:
--------------------------------

SUCCESS: Integrated in HBase-1.3-IT #139 (See 
[https://builds.apache.org/job/HBase-1.3-IT/139/])
HBASE-14322 Add a master priority function to let master use it's threads 
(eclark: rev 5b6a46237b6376ee63a3c87d2a67a05f987e44af)
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterRpcServices.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterAnnotationReadingPriorityFunction.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestQosFunction.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterQosFunction.java
* hbase-server/src/test/java/org/apache/hadoop/hbase/QosTestHelper.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/AnnotationReadingPriorityFunction.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java


> Master still not using more than it's priority threads
> ------------------------------------------------------
>
>                 Key: HBASE-14322
>                 URL: https://issues.apache.org/jira/browse/HBASE-14322
>             Project: HBase
>          Issue Type: Sub-task
>          Components: master, rpc
>    Affects Versions: 1.2.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>             Fix For: 2.0.0, 1.2.0
>
>         Attachments: HBASE-14322-v1.patch, HBASE-14322-v2.patch, 
> HBASE-14322-v3-branch-1.patch, HBASE-14322-v3.patch, 
> HBASE-14322-v4-branch-1.patch, HBASE-14322-v5-branch-1.patch, 
> HBASE-14322-v6.patch, HBASE-14322-v7.patch, HBASE-14322.patch
>
>
> Master and regionserver will be running as the same user.
> Superusers by default adds the current user as a super user.
> Super users' requests always go to the priority threads.



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

Reply via email to