[jira] [Commented] (CASSANDRA-5037) Set CASSANDRA_HEAPDUMP_DIR in cassandra-env.sh by default

["Sven Delmas (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607185#comment-13607185 ] 

Sven Delmas commented on CASSANDRA-5037:
----------------------------------------

I am happy to adjust the redhat init file we use in dsc accordingly, but who would change ./debian/init then (that's C* packaging correct)?
                
> Set CASSANDRA_HEAPDUMP_DIR in cassandra-env.sh by default
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-5037
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5037
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Config
>    Affects Versions: 1.1.7, 1.2.0 beta 3
>            Reporter: J.B. Langston
>            Priority: Minor
>
> Cassandra is configured via -XX:+HeapDumpOnOutOfMemoryError to trigger a heap dump at the occurrence of an OutOfMemoryError, but unless you have set your CASSANDRA_HEAPDUMP_DIR in cassandra-env.sh, the file will be written in the Cassandra process's working directory, which when Cassandra is run as a service is typically the root directory. Nine times out of ten, the Cassandra process does not have permission to write here so no heap dump is created. Even if Cassandra does have permission, the root filesystem is usually small and the heap dump could easily fill it up with a large Xmx configured. This makes post-mortem analysis difficult. We should set it by default to e.g. /var/log/cassandra.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira