You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeremiah Jordan (JIRA)" <ji...@apache.org> on 2014/01/09 17:02:54 UTC

[jira] [Updated] (CASSANDRA-6541) Add JVM_OPTS="$JVM_OPTS -XX:+CMSClassUnloadingEnabled" to cassandra-env.sh

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

Jeremiah Jordan updated CASSANDRA-6541:
---------------------------------------

    Description: 
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.

  was:Newer versions of Oracle's Hotspot JVM , post 6u45, 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.  Running repair exacerbates this issue.  The configuration added to the Summary line helps alleviate this behavior and should be included in the C* config files by default.


> Add JVM_OPTS="$JVM_OPTS -XX:+CMSClassUnloadingEnabled" to cassandra-env.sh
> --------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6541
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6541
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Config
>            Reporter: jonathan lacefield
>            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)