[
https://issues.apache.org/jira/browse/HDFS-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524737#comment-14524737
]
Hadoop QA commented on HDFS-5639:
---------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12617519/HDFS-5639-2.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f1a152c |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/10582/console |
This message was 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.3.4#6332)
