[
https://issues.apache.org/jira/browse/HADOOP-10125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13830493#comment-13830493
]
Hadoop QA commented on HADOOP-10125:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12615427/hadoop_10125_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3311//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3311//console
This message is automatically generated.
> no need to process RPC request if the client connection has been dropped
> ------------------------------------------------------------------------
>
> Key: HADOOP-10125
> URL: https://issues.apache.org/jira/browse/HADOOP-10125
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Ming Ma
> Attachments: hadoop_10125_trunk.patch
>
>
> If the client has dropped the connection before the RPC is processed, RPC
> server doesn't need to process the RPC call. We have encountered issues where
> bad applications can bring down the NN.
> https://issues.apache.org/jira/i#browse/Hadoop-9640 tries to address that.
> When this occurs, NN's RPC queues are filled up with client requests and DN
> requests, sometimes we want to stop the flooding by stopping the bad
> applications and/or DNs. Some RPC processing like
> DatanodeProtocol::blockReport could take couple hundred milliseconds. So it
> is worthwhile to have NN skip the RPC calls if DNs have been stopped.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
