[
https://issues.apache.org/jira/browse/HDFS-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268614#comment-13268614
]
Todd Lipcon commented on HDFS-3373:
-----------------------------------
Nicholas had some ideas about this in HDFS-3359. Quoting here:
{quote}
I think we should either
- change it from per DFSClient to per DFSInputStream; or
- change it to a global static cache (like what we did for LeaseRenewer.)
{quote}
Brainstorming: maybe another option would be to have a timer thread which
periodically wakes up and scans SocketCaches for old sockets. If any socket has
been sitting around longer than a minute or two, we can close it proactively.
> 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
