[jira] [Updated] (PIG-4603) Classloader leak in SpillableMemoryManager

["Rohini Palaniswamy (JIRA)" <ji...@apache.org>]

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

Rohini Palaniswamy updated PIG-4603:
------------------------------------
    Fix Version/s: 0.16.0
         Assignee: Rohini Palaniswamy

   No problem. We just offer the reporter of the issue the first chance to fix it as well :).  Did you find the issue with Tez container reuse?

> Classloader leak in SpillableMemoryManager
> ------------------------------------------
>
>                 Key: PIG-4603
>                 URL: https://issues.apache.org/jira/browse/PIG-4603
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: 0.15.0
>            Reporter: Gleb Smirnov
>            Assignee: Rohini Palaniswamy
>             Fix For: 0.16.0
>
>
> In the constructor of {{SpillableMemoryManager}}, a {{NotificationListener}} is added to the {{MemoryMXBean}}. This listener is never removed, even if the application is re-deployed.
> This results in the instance {{SpillableMemoryManager}} being still reachable after a redeploy. This results in its class being reachable, which results in the classloader being reachable, along with all the classes in it.
> This leads to metaspace OutOfMemoryErrors.



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