[
https://issues.apache.org/jira/browse/HADOOP-7973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187756#comment-13187756
]
Nathan Roberts commented on HADOOP-7973:
----------------------------------------
{quote}
We'll experiment on a performance grid and see what happens with the cache off.
I'm concerned about whether GC will keep up with all the leaked FileSystem and
DFSClient objects.
{quote}
Seems to me that turning off the cache is changing the semantics of
FileSystem#close as much as some of the other proposed solutions. Rather than
just temporarily avoiding this issue via a config change, can we come up with a
more permanent solution that everyone will be happy with?
> 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
