[
https://issues.apache.org/jira/browse/HDFS-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465718#comment-13465718
]
John George commented on HDFS-3373:
-----------------------------------
In 2.0, setting cache capacity to 0 disabled the cache, this (along with some
other changes) was not in 0.23. TestSocketCache was a one test file to test if
cache disabling worked. Since, 0.23 does not have that, I did not port the test.
> 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: 0.23.3, 2.0.0-alpha, 3.0.0
> Reporter: Todd Lipcon
> Assignee: John George
> Fix For: 2.0.3-alpha
>
> Attachments: HDFS-3373.branch-23.patch, HDFS-3373.branch23.patch,
> HDFS-3373.trunk.patch, HDFS-3373.trunk.patch.1, HDFS-3373.trunk.patch.2,
> HDFS-3373.trunk.patch.3, HDFS-3373.trunk.patch.3, HDFS-3373.trunk.patch.4
>
>
> 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
