cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-9861) When forcibly exiting due to OOM, we should produce a heap dump
Date Mon, 21 Mar 2016 14:03:25 GMT

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

Benjamin Lerer edited comment on CASSANDRA-9861 at 3/21/16 2:02 PM:
--------------------------------------------------------------------

I guess the simplest way would be to add the {{-XX:+HeapDumpOnOutOfMemoryError}}  command
line argument to our startup scripts.


was (Author: blerer):
I guess the simplest way would be to use the {{-XX:+HeapDumpOnOutOfMemoryError}}  command
line argument to our startup scripts.

> When forcibly exiting due to OOM, we should produce a heap dump
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-9861
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9861
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Benedict
>            Priority: Minor
>              Labels: lhf
>             Fix For: 2.2.x
>
>
> CASSANDRA-7507 introduced earlier termination on encountering an OOM, due to lack of
certainty about system state. However a side effect is that we never produce heap dumps on
OOM. We should ideally try to produce one forcibly before exiting.



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

Mime
View raw message