cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7638) Revisit GCInspector
Date Fri, 01 Aug 2014 17:17:38 GMT

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

Jeremiah Jordan commented on CASSANDRA-7638:
--------------------------------------------

bq. For ParNew the cause is always  "Allocation Failure." Duh. 
bq. "CMS Initial Mark" isn't particularly enlightening either 

I think it is useful to have that there, if when there is a full GC from a ParNew "promotion
failure" or CMS "concurrent mode failure" it tells you that.

> Revisit GCInspector
> -------------------
>
>                 Key: CASSANDRA-7638
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7638
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>            Priority: Minor
>             Fix For: 2.1.0
>
>         Attachments: 7638-v2.txt, 7638.txt
>
>
> In CASSANDRA-2868 we had to change the api that GCI uses to avoid the native memory leak,
but this caused GCI to be less reliable and more 'best effort' than before where it was 100%
reliable.  Let's revisit this and see if the native memory leak is fixed in java7.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message