cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7638) Revisit GCInspector
Date Thu, 31 Jul 2014 20:47:39 GMT

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

Yuki Morishita commented on CASSANDRA-7638:
-------------------------------------------

I wonder if GC JMX notification can be used for accuracy.
I experimented this a year ago (pushded to https://github.com/yukim/cassandra/tree/gc_notification),
but due to the bug in JDK(http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7087969) I set
aside.

Just FYI.

> 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.0.10
>
>         Attachments: 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