[ https://issues.apache.org/jira/browse/HDFS-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842073#comment-13842073 ]
Hadoop QA commented on HDFS-5639: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12617519/HDFS-5639-2.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 9 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 core tests{color}. The patch failed these unit tests in hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.hdfs.server.blockmanagement.TestBlocksWithNotEnoughRacks {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/5671//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5671//console This message is automatically generated. > rpc scheduler abstraction > ------------------------- > > Key: HDFS-5639 > URL: https://issues.apache.org/jira/browse/HDFS-5639 > Project: Hadoop HDFS > Issue Type: Improvement > Reporter: Ming Ma > Attachments: HDFS-5639-2.patch, HDFS-5639.patch > > > We have run into various issues in namenode and hbase w.r.t. rpc handling in > multi-tenant clusters. The examples are > https://issues.apache.org/jira/i#browse/HADOOP-9640 > https://issues.apache.org/jira/i#browse/HBASE-8836 > There are different ideas on how to prioritize rpc requests. It could be > based on user id, or whether it is read request or write request, or it could > use specific rule like datanode's RPC is more important than client RPC. > We want to enable people to implement and experiiment different rpc > schedulers. -- This message was sent by Atlassian JIRA (v6.1#6144)