hadoop-hdfs-issues mailing list archives

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

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

Daryn Sharp commented on HDFS-3373:
-----------------------------------

A related issue we need to consider, although tangental is that inability to {{close}} doesn't
give a fs a chance to cleanup.  Ex. closing streams and deleting temp files.  I think there
might be another jira for that?
                
> 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-alpha
>            Reporter: Todd Lipcon
>            Assignee: John George
>         Attachments: HDFS-3373.branch-23.patch
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message