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] [Resolved] (CASSANDRA-9604) Upon JVM OOM (Out Of Memory), print out a summary of heap histograms in addition to heap dump
Date Wed, 06 Apr 2016 12:03:25 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-9604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Benjamin Lerer resolved CASSANDRA-9604.
---------------------------------------
    Resolution: Duplicate

CASSANDRA-9861 will ensure that an heap histogram is logged after the heap dump has been generated.

> Upon JVM OOM (Out Of Memory), print out a summary of heap histograms in addition to heap
dump
> ---------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-9604
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9604
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Configuration
>            Reporter: Wei Deng
>            Priority: Minor
>
> It appears that jmap has an option to allow dumping heap histograms after a heap dump
is generated (http://www.oracle.com/technetwork/java/javase/memleaks-137499.html#gbywi). This
could be useful to provide a very quick overview of the biggest objects in heap without having
to download the massive hprof file off the Cassandra nodes. We can potentially hook it up
using this JVM option: -XX:OnOutOfMemoryError="<cmd args>; <cmd args>" in the
cassandra-env.sh file.



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

Mime
View raw message