[CASSANDRA-6541] 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.

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 1.2.16, 2.0.6, 2.1 beta2
• Component/s: Local/Config
• Severity: Low
• Assignee: Brandon Williams
• Reporter: jonathan lacefield

Authors

Brandon Williams

Reviewers

Michael Shuler

• Created: 02/Jan/14 20:38
• Updated: 16/Apr/19 09:31
• Resolved: 26/Mar/15 20:50

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:

JVM_OPTS="$JVM_OPTS -XX:+CMSClassUnloadingEnabled"

The the options in cassandra-env.sh alleviates the problem.

Issue Links

• links to: GitHub Pull Request #236