You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yogesh Nachnani (JIRA)" <ji...@apache.org> on 2017/04/28 01:50:04 UTC
[jira] [Updated] (CASSANDRA-12849) The parameter -XX:HeapDumpPath
is not ovewritten by cassandra-env.sh
[ https://issues.apache.org/jira/browse/CASSANDRA-12849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yogesh Nachnani updated CASSANDRA-12849:
----------------------------------------
Attachment: 12849-trunk.txt
It seems the user would have used the -H option while running bin/cassandra The -H option is processed after processing cassandra-env.sh ; hence-fence the override behaviour.
[~carlo_4002] - Do let me know exactly how your process is started, so we can eliminate any other remaining bugs.
Also changed the documentation to nudge users to use cassandra-env.sh rather than specifying JVM_OPTS on the command line
> The parameter -XX:HeapDumpPath is not ovewritten by cassandra-env.sh
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-12849
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12849
> Project: Cassandra
> Issue Type: Bug
> Reporter: jean carlo rivera ura
> Labels: lhf
> Attachments: 12849-trunk.txt
>
>
> 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org