You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "anmols (JIRA)" <ji...@apache.org> on 2016/12/06 15:19:59 UTC

[jira] [Created] (CASSANDRA-13006) Disable automatic heap dumps on OOM error

anmols created CASSANDRA-13006:
----------------------------------

             Summary: Disable automatic heap dumps on OOM error
                 Key: CASSANDRA-13006
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13006
             Project: Cassandra
          Issue Type: Bug
          Components: Configuration
            Reporter: anmols
            Priority: Minor


With CASSANDRA-9861, a change was added to enable collecting heap dumps by default if the process encountered an OOM error. These heap dumps are stored in the Apache Cassandra home directory unless configured otherwise (see [Cassandra Support Document|https://support.datastax.com/hc/en-us/articles/204225959-Generating-and-Analyzing-Heap-Dumps] for this feature).
 
The creation and storage of heap dumps aides debugging and investigative workflows, but is not be desirable for a production environment where these heap dumps may occupy a large amount of disk space and require manual intervention for cleanups. 
 
Managing heap dumps on out of memory errors and configuring the paths for these heap dumps are available as JVM options in JVM. The current behavior conflicts with the Boolean JVM flag HeapDumpOnOutOfMemoryError. 
 
A patch can be proposed here that would make the heap dump on OOM error honor the HeapDumpOnOutOfMemoryError flag. Users who would want to still generate heap dumps on OOM errors can set the -XX:+HeapDumpOnOutOfMemoryError JVM option.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)