jean carlo rivera ura created CASSANDRA-12849:
-------------------------------------------------
Summary: The parameter -XX:HeapDumpPath is not ovewritten by
cassandra-end.sh
Key: CASSANDRA-12849
URL: https://issues.apache.org/jira/browse/CASSANDRA-12849
Project: Cassandra
Issue Type: Bug
Reporter: jean carlo rivera ura
The parameter -XX:HeapDumpPath appears twice in the java process
{panel}
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
org.apache.cassandra.service.CassandraDaemon
{panel}
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 cassandra-env.sh
*/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 in cassandra-env.sh
{noformat}
user@node:~$ jmx4perl http://localhost:8523/jolokia read
com.sun.management:type=HotSpotDiagnostic DiagnosticOptions
{
name => 'HeapDumpPath',
origin => 'VM_CREATION',
value => '/home/cassandra/java_1477043835.hprof',
writeable => '[true]'
},
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
