hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10125) no need to process RPC request if the client connection has been dropped
Date Fri, 17 Jan 2014 11:11:08 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-10125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874674#comment-13874674

Hudson commented on HADOOP-10125:

SUCCESS: Integrated in Hadoop-Yarn-trunk #455 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/455/])
backported HADOOP-10125 to branch2, update CHANGES.txt (brandonli: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1558953)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt

> 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, 2.4.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

View raw message