You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Rajesh Balamohan (JIRA)" <ji...@apache.org> on 2014/09/15 10:24:33 UTC

[jira] [Updated] (TEZ-1585) Memory leak in tez session mode

     [ https://issues.apache.org/jira/browse/TEZ-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajesh Balamohan updated TEZ-1585:
----------------------------------
    Attachment: app_master.tar.gz

Attaching jprofiler profiler output for reference.

Simple DAG (M->R) was run repeatedly to reproduce this case. 

> 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)