accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-1379) PermGen leak
Date Tue, 10 Sep 2013 20:59:51 GMT

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

John Vines updated ACCUMULO-1379:
---------------------------------

    Attachment: ACCUMULO-1379_v2.patch

Attaching a revised patch which deals with thrift. The plumbing for thrift feels a bit weird
since a lot of our thrift accesses (including that which creates the Daemon) is in static
methods, but I did work it through ThriftUtils so it seems a bit consistent. Going to let
this sit for a day or 3 before I commit to see if there are better ideas.

And yes, I did test it and after jstacking some code which did a METADATA scan, I had no standing
Accumulo threads active. So I deem it a success.
                
>  PermGen leak 
> --------------
>
>                 Key: ACCUMULO-1379
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1379
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.4.3, 1.5.0
>         Environment: Linux/JBoss
>            Reporter: Mike Giordano
>            Assignee: John Vines
>             Fix For: 1.6.0
>
>         Attachments: ACCUMULO-1379.patch, ACCUMULO-1379_v2.patch
>
>
> Under version 1.3.7 we are using the following code to initialize a cloudbase connection
during initialization of our web app:
>                         ZooKeeperInstance instance = new ZooKeeperInstance(instanceName,
zooKeepers);
>                         connector = instance.getConnector(userId, password.getBytes());
> The problem is that under the hood, this call creates several threads that are not cleaned
up when the app is undeployed in JBoss. This is occurring without performing any scans or
interacting with cloudbase in any other way. After relatively few redeploys of the app, the
PermGen Space is OOM.
> I can't find any reference in the cloudbase API akin to a close() method for the Connector
object. This is a classloader leak effecting any webapp that is accessing cloudbase directly.
The result of this leak is not simply orphaned threads, but thousands of classes not gc'd
because the classloader itself can't be gc'd. This is what is filling up PermGen.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message