[
https://issues.apache.org/jira/browse/CASSANDRA-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916367#comment-13916367
]
Michael Shuler commented on CASSANDRA-6541:
-------------------------------------------
I get no complaints using -XX:+CMSClassUnloadingEnabled with 1.5.0_22-b03 and
found an old doc that lists this VM option available in 1.4.1 1.4.2 1.5.0 1.6.0
- http://www.reins.altervista.org/java/A_Collection_of_JVM_Options_MP.html
I'd say it's probably pretty safe to add it.
> New versions of Hotspot create new Class objects on every JMX connection
> causing the heap to fill up with them if CMSClassUnloadingEnabled isn't set.
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-6541
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6541
> Project: Cassandra
> Issue Type: Bug
> Components: Config
> Reporter: jonathan lacefield
> Assignee: Michael Shuler
> Priority: Minor
>
> Newer versions of Oracle's Hotspot JVM , post 6u43 (maybe earlier) and 7u25
> (maybe earlier), are experiencing issues with GC and JMX where heap slowly
> fills up overtime until OOM or a full GC event occurs, specifically when CMS
> is leveraged. Adding:
> {noformat}
> JVM_OPTS="$JVM_OPTS -XX:+CMSClassUnloadingEnabled"
> {noformat}
> The the options in cassandra-env.sh alleviates the problem.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
