cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9861) When forcibly exiting due to OOM, we should produce a heap dump
Date Sat, 02 Apr 2016 17:44:25 GMT

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

Robert Stupp commented on CASSANDRA-9861:
-----------------------------------------

There's {{org.hyperic.sigar.Sigar#getPid}} to get the process ID.
Maybe we should use {{jmap}} from {{System.getProperty("java.home") + "/bin/jmap"}} (resp.
{{jmap.exe}}) and only use {{map}}/{{jmap.exe}} as a fallback.


> 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
>          Components: Lifecycle
>            Reporter: Benedict
>            Assignee: Benjamin Lerer
>            Priority: Minor
>              Labels: lhf
>             Fix For: 2.2.x
>
>         Attachments: 9861-2.2.txt
>
>
> 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