[
https://issues.apache.org/jira/browse/HADOOP-10125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13872693#comment-13872693
]
Hudson commented on HADOOP-10125:
---------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #5005 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5005/])
HADOOP-10125. no need to process RPC request if the client connection has been
dropped. Contributed by Min Ma (brandonli:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1558575)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java
> 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
> Components: ipc
> Affects Versions: 3.0.0
> Reporter: Ming Ma
> Assignee: Ming Ma
> Fix For: 3.0.0
>
> 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.5#6160)
