[
https://issues.apache.org/jira/browse/HADOOP-7973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185849#comment-13185849
]
Suresh Srinivas commented on HADOOP-7973:
-----------------------------------------
bq. Isn't this going to cause multiple sockets to the same namenode? For code
that doesn't explicitly call close (perhaps because of this bug), that results
in leaked fds that tie up resources. I vaguely seem to recall that disabling
the cache for a job would cause the JT to overwhelm the namenode with
connections.
Connections are reused right? So this should not be an issue. I remember having
some issue related to having file system cache growing huge and causing memory
issues. That could still happen. Not sure how this bug was fixed.
> DistributedFileSystem close has severe consequences
> ---------------------------------------------------
>
> Key: HADOOP-7973
> URL: https://issues.apache.org/jira/browse/HADOOP-7973
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 1.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Blocker
> Attachments: HADOOP-7973.patch
>
>
> The way {{FileSystem#close}} works is very problematic. Since the
> {{FileSystems}} are cached, any {{close}} by any caller will cause problems
> for every other reference to it. Will add more detail in the comments.
--
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
