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

Siddharth Seth commented on TEZ-1585:
-------------------------------------

An alternate may be to do a FileSystem.closeAllForUGI once a DAG completes. 
This is what is done in TezChild.
THis should ideally work correctly on secure clusters as well.

> Memory leak in tez session mode
> -------------------------------
>
>                 Key: TEZ-1585
>                 URL: https://issues.apache.org/jira/browse/TEZ-1585
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Rajesh Balamohan
>         Attachments: app_master.tar.gz
>
>
> DAGAppMaster's memory gradually keeps increasing when running simple tez apps 
> repeatedly in session mode.  Taking memory snapshots revealed that 
> FileSystem.CACHE is getting populated with some keys which are not being 
> released.  
> Around 200KB of data is leaked for every job invocation in the session mode.  
> I will attach the profiler snapshots soon.  Haven't figured out yet on who 
> makes the call to FileSystem.get() and not calling close().



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to