[
https://issues.apache.org/jira/browse/CASSANDRA-9861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-9861:
--------------------------------------
Attachment: 9861-2.2-V2.txt
The new patch try to use Sigar for retrieving the pid and default to parsing
the JVM name if Sigar is not initialized (which is the case on my machine).
It also try to resolve the path to jmap from JAVA_HOME and default to jmap if
the file cannot be found.
After the heap as been dumped an heap histogram will be writting to the log
file.
> 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-V2.txt, 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)
