[
https://issues.apache.org/jira/browse/ACCUMULO-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279191#comment-13279191
]
John Vines commented on ACCUMULO-599:
-------------------------------------
Perhaps this should be a generic look into java garbage collection
configurations. It's been a while since we have done research into that
subject.
Sent from my phone, so pardon the typos and brevity.
> investigate permgen collection and class unloading with concurrent mark and
> sweep garbage collector
> ---------------------------------------------------------------------------------------------------
>
> Key: ACCUMULO-599
> URL: https://issues.apache.org/jira/browse/ACCUMULO-599
> Project: Accumulo
> Issue Type: Bug
> Components: scripts
> Affects Versions: 1.3.6, 1.4.0
> Reporter: Adam Fuchs
> Assignee: John Vines
>
> The Java concurrent mark and sweep garbage collector appears to default to
> not unloading classes or sweeping the permgen storage space. Accumulo reloads
> classes dynamically, potentially contributing a lot to the permgen space. It
> is important that these classes be garbage collected when we're done with
> them. Since we use -XX:+UseConcMarkSweepGC by default for all Accumulo
> processes, should we also use -XX:+CMSClassUnloadingEnabled and
> -XX:+CMSPermGenSweepingEnabled? Are there other flags or parameters that we
> should set to really do java garbage collection properly in a long-lived
> instance?
> These should be set in conf/accumulo-env.sh as part of ACCUMULO_GENERAL_OPTS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
