cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jean carlo rivera ura (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-12849) The parameter -XX:HeapDumpPath is not ovewritten by
Date Thu, 27 Oct 2016 14:43:59 GMT
jean carlo rivera ura created CASSANDRA-12849:

             Summary: The parameter  -XX:HeapDumpPath is not ovewritten by
                 Key: CASSANDRA-12849
             Project: Cassandra
          Issue Type: Bug
            Reporter: jean carlo rivera ura

The parameter  -XX:HeapDumpPath appears twice in the java process 
user@node:~$ sudo ps aux | grep --color  HeapDumpPath

java -ea -javaagent:/usr/share/cassandra/lib/jamm-0.3.0.jar -XX:+CMSClassUnloadingEnabled
-XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1024M -Xmx1024M -Xmn200M -XX:+HeapDumpOnOutOfMemoryError
-XX:*HeapDumpPath*=/var/lib/cassandra-1477577769-pid1516.hprof -Xss256k 
-XX:*HeapDumpPath*=/home/cassandra/java_1477577769.hprof -XX:ErrorFile=/var/lib/cassandra/hs_err_1477577769.log

The problem is when we have an OOM error, the JVM dump goes to */home/cassandra/java_1477577769.hprof
* when the correct behavior is to go to the path defined by  */var/lib/cassandra-1477577769-pid1516.hprof*

This is quite annoying because cassandra takes into account only the path defined by the script
init (usually that disk is not that big to keep 8Gb of a heap dump) and not the path defined

user@node:~$ jmx4perl http://localhost:8523/jolokia read
        name => 'HeapDumpPath',
        origin => 'VM_CREATION',
        value => '/home/cassandra/java_1477043835.hprof',
        writeable => '[true]'


This message was sent by Atlassian JIRA

View raw message