Return-Path: 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 EBD3D17DCA for ; Thu, 9 Apr 2015 09:40:13 +0000 (UTC) Received: (qmail 64398 invoked by uid 500); 9 Apr 2015 09:40:13 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 64357 invoked by uid 500); 9 Apr 2015 09:40:13 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 64341 invoked by uid 99); 9 Apr 2015 09:40:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Apr 2015 09:40:13 +0000 Date: Thu, 9 Apr 2015 09:40:13 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: 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=14487049#comment-14487049 ] Hadoop QA commented on HBASE-13375: ----------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12724149/HBASE-13375-v1.patch against master branch at commit 80dbf06651e527ec0421ce51e4712ffb2f1d078b. ATTACHMENT ID: 12724149 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 22 new or modified tests. {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions (2.4.1 2.5.2 2.6.0) {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 protoc{color}. The applied patch does not increase the total number of protoc compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 checkstyle{color}. The applied patch does not increase the total number of checkstyle errors {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 lineLengths{color}. The patch does not introduce lines longer than 100 {color:red}-1 site{color}. The patch appears to cause mvn site goal to fail. {color:red}-1 core tests{color}. The patch failed these unit tests: org.apache.hadoop.hbase.util.TestProcessBasedCluster org.apache.hadoop.hbase.mapreduce.TestImportExport {color:red}-1 core zombie tests{color}. There are 1 zombie test(s): at org.apache.oozie.test.MiniHCatServer$1.run(MiniHCatServer.java:137) at org.apache.oozie.test.XTestCase$MiniClusterShutdownMonitor.run(XTestCase.java:1071) at org.apache.oozie.test.XDataTestCase.writeToFile(XDataTestCase.java:1206) at org.apache.oozie.test.XDataTestCase.getCoordConf(XDataTestCase.java:1197) at org.apache.oozie.test.XDataTestCase.createCoordAction(XDataTestCase.java:694) at org.apache.oozie.test.XDataTestCase.createCoordAction(XDataTestCase.java:638) at org.apache.oozie.executor.jpa.TestCoordActionGetForTimeoutJPAExecutor.testCoordActionGet(TestCoordActionGetForTimeoutJPAExecutor.java:54) Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/13643//testReport/ Release Findbugs (version 2.0.3) warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/13643//artifact/patchprocess/newFindbugsWarnings.html Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/13643//artifact/patchprocess/checkstyle-aggregate.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/13643//console This message is automatically generated. > 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.0 > > Attachments: HBASE-13375-v0.patch, HBASE-13375-v1.patch, HBASE-13375-v1.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)