You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (Jira)" <ji...@apache.org> on 2021/07/21 15:13:00 UTC
[jira] [Updated] (CASSANDRA-13843) Debian init shadows
CASSANDRA_HEAPDUMP_DIR
[ https://issues.apache.org/jira/browse/CASSANDRA-13843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-13843:
-----------------------------------------
Fix Version/s: (was: 4.x)
4.0.x
3.0.x
> Debian init shadows CASSANDRA_HEAPDUMP_DIR
> ------------------------------------------
>
> Key: CASSANDRA-13843
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13843
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Observability
> Reporter: Andrew Jorgensen
> Priority: Low
> Labels: newbie, patch
> Fix For: 3.0.x, 3.11.x, 4.0.x
>
> Attachments: 0001-Remove-debian-init-setting-heap-dump-file.patch
>
>
> The debian init script sets the heap dump file directly using the cassandra users home directory and the -H flag to the cassandra process[1|https://github.com/apache/cassandra/blob/8b3a60b9a7dbefeecc06bace617279612ec7092d/debian/init#L76]. The cassandra heap dump location can also be set in the cassandra-env.sh file using CASSANDRA_HEAPDUMP_DIR. Unfortunately the debian init heap dump location is based off the home directory of the cassandra user and cannot easily be changed. Also unfortunately if you do `ps aux | grep casandra` you can clearly see that the -H flag takes precedent over the value found in cassandra-env.sh. This makes it difficult to change the heap dump location for cassandra and is non-intuitive when the value is set in cassandra-env.sh why the heap dump does not actually end up in the correct place.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org