[jira] [Commented] (HADOOP-10613) Potential Resource Leaks in FileSystem.CACHE

["Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-10613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001359#comment-14001359 ] 

Tsz Wo Nicholas Sze commented on HADOOP-10613:
----------------------------------------------

> ... If every time i use a new UGI object to invoke FileSystem.get(conf) and never invoke FileSystem's close method,this issue will raise.
 ...

Is it similar to if an application open a lot of (local) files but not closing them, or open a lot of sockets but not closing them?  I think the application is responsible to call close() for releasing the resource in such cases.

> Potential Resource Leaks in FileSystem.CACHE 
> ---------------------------------------------
>
>                 Key: HADOOP-10613
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10613
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 2.4.0
>            Reporter: Nemon Lou
>
> There is no size limit of the hashmap in  FileSystem.CACHE, which can cause a potential memory leak.
> If every time i use a new UGI object to invoke FileSystem.get(conf)  and never invoke FileSystem's close method,this issue will raise.
> If there is a size limit of the hashmap or changing fileSystem instances to soft reference,then user's code don't need to consider too much about the cache leak issues.



--
This message was sent by Atlassian JIRA
(v6.2#6252)