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 "Arun C Murthy (Updated) (JIRA)" <ji...@apache.org> on 2012/03/05 03:45:04 UTC

[jira] [Updated] (HADOOP-7317) RPC.stopProxy doesn't actually close proxy

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

Arun C Murthy updated HADOOP-7317:
----------------------------------

    Fix Version/s:     (was: 0.23.1)
                   0.23.3
    
> RPC.stopProxy doesn't actually close proxy
> ------------------------------------------
>
>                 Key: HADOOP-7317
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7317
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>             Fix For: 0.23.3
>
>
> Discovered while investigating HDFS-1965, it turns out that the reference-counting done in WritableRpcEngine.ClientCache doesn't map one-to-one with open TCP connections. This means that it's easy to accidentally leave TCP connections open longer than expected so long as the client has any other connections open at all.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira