cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13006) Disable automatic heap dumps on OOM error
Date Mon, 12 Dec 2016 10:56:58 GMT


Benjamin Lerer commented on CASSANDRA-13006:

One thing that I did not consider why working on CASSANDRA-9861 was that not everybody use
the Oracle JVM. It is clear that some people use {{Zing}} and I guess that some people might
also be using the IBM JVM. All of those JVM seems to provide {{jmap}} but they do not seems
to use the same configuration arguments for handling {{OOM}} errors. I could not find the
{{Zing}} options ([~nitsanw] do you have any idea of where I could get them?) but the IBM
JVM does not use the same options as the Oracle one.
Moreover, the Oracle JVM support also options like {{-XX:OnOutOfMemoryError}} which we currently

To be honest, I am not fully sure how we should handle all that. We could:
# try to determine which JVM is being used and check for the relevants options (knowing that
it will never be fully bulletproof)
# ignore the JVM options and create our own configuration for it (knowing that it might be
confusing for the administrators)

Any opinions or suggestions?    

> Disable automatic heap dumps on OOM error
> -----------------------------------------
>                 Key: CASSANDRA-13006
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Configuration
>            Reporter: anmols
>            Assignee: Benjamin Lerer
>            Priority: Minor
>             Fix For: 3.0.9
>         Attachments: 13006-3.0.9.txt
> 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|]
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

This message was sent by Atlassian JIRA

View raw message