hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3373) FileContext HDFS implementation can leak socket caches
Date Mon, 07 May 2012 17:38:48 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269804#comment-13269804
] 

Todd Lipcon commented on HDFS-3373:
-----------------------------------

No, I don't think so, because we also now have a fix on the DN side which closes the sockets.
So it might result in TIME_WAIT or FIN_WAIT sockets on the client, but shouldn't impact DNs
anymore. Unless someone has seen this to be a production issue with 2.0, it shouldn't be considered
blocker.
                
> FileContext HDFS implementation can leak socket caches
> ------------------------------------------------------
>
>                 Key: HDFS-3373
>                 URL: https://issues.apache.org/jira/browse/HDFS-3373
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 2.0.0
>            Reporter: Todd Lipcon
>
> As noted by Nicholas in HDFS-3359, FileContext doesn't have a close() method, and thus
never calls DFSClient.close(). This means that, until finalizers run, DFSClient will hold
on to its SocketCache object and potentially have a lot of outstanding sockets/fds held on
to.

--
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

        

Mime
View raw message