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

Posted to commits@cassandra.apache.org by "Benjamin Lerer (JIRA)" <ji...@apache.org> on 2016/03/21 13:40:25 UTC

[jira] [Commented] (CASSANDRA-9861) When forcibly exiting due to OOM, we should produce a heap dump

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

Benjamin Lerer commented on CASSANDRA-9861:
-------------------------------------------

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)