[ https://issues.apache.org/jira/browse/HADOOP-7973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188025#comment-13188025 ]
Daryn Sharp commented on HADOOP-7973: ------------------------------------- bq. It is correct that connections are re-used and cache growing huge is also an issue that we have seen before. It was fixed by calling closeAllForUGI in TaskTracker. If the cache is turned off, doesn't the {{FileSystem.closeAllForUGI}} improvement become irrelevant since it depends on the cache to locate the objects to close? Ie. Won't the {{FileSystem}}, {{DFSClient}}, and {{Connection}} float in limbo and bloat memory until the GC finalizes them? > 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