hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7317) RPC.stopProxy doesn't actually close proxy
Date Tue, 23 Aug 2011 19:38:28 GMT

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

Uma Maheswara Rao G commented on HADOOP-7317:

This will create issues when clients are trying to switch the NNs in HA.
We used to get the EOFExceptions when we just do stopProxy and recreate again. Observation
is that, sometimes it was getting old references as well. Call on that old referances were
getting EOFExceptions.
Shall we provide an API on client which will destroy completely?


> 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.22.0
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message