[
https://issues.apache.org/jira/browse/PIG-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588674#comment-14588674
]
Rohini Palaniswamy commented on PIG-4603:
-----------------------------------------
I realized that it cannot be a problem with Tez container reuse. Can you
clarify "redeploy" ? Is it on the pig client side? Are they deploying Pig in
some webapp and hence the multiple classloaders?
> 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)
