[CASSANDRA-12849] The parameter -XX:HeapDumpPath is not ovewritten by cassandra-env.sh

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Component/s: Local/Config
• Labels: lhf
• Severity: Normal
• Complexity: Low Hanging Fruit
• Since Version: 2.1.14
• Assignee: Unassigned
• Reporter: jean carlo rivera ura
• Created: 27/Oct/16 14:43
• Updated: 21/Jul/21 19:52
• Resolved: 21/Jul/21 19:52

Description

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 org.apache.cassandra.service.CassandraDaemon

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

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]'
      },

Issue Links

• duplicates: CASSANDRA-13843 Debian init shadows CASSANDRA_HEAPDUMP_DIR