You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Brandon Li (JIRA)" <ji...@apache.org> on 2014/01/15 22:49:24 UTC

[jira] [Updated] (HADOOP-10125) no need to process RPC request if the client connection has been dropped

     [ https://issues.apache.org/jira/browse/HADOOP-10125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Li updated HADOOP-10125:
--------------------------------

    Assignee: Ming Ma

> 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
>            Assignee: 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.5#6160)