[
https://issues.apache.org/jira/browse/HADOOP-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054642#comment-14054642
]
Steve Loughran commented on HADOOP-10792:
-----------------------------------------
I feel your pain, as I've hit it too. You can ask for a non-shared copy of a
FileSystem instance by setting the property "fs.%s.impl.disable.cache" for the
config you use when you ask for the FS. I recommend you do that in libraries,
or rely on the JVM shutdown logic to trigger cleanup.
> Add FileSystem#closeIfNotReferred method
> ----------------------------------------
>
> Key: HADOOP-10792
> URL: https://issues.apache.org/jira/browse/HADOOP-10792
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Reporter: Kousuke Saruta
>
> FileSystem#close closes FileSystem even if the same instance of FileSystem is
> referred by someone.
> For instance, a library using FileSystem calls FileSystem.get, and a program
> using the library calls FileSystem.get, both of instances of FileSystem is
> same.
> When the library and the program is implemented as different threads and one
> calls FileSystem.close, another fails most of operations of FileSystem.
> So, we need the method like cloesIfNotReferred, which closes FileSystem only
> if a instance of FileSystem is not referred by anyone.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
