Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 1 Aug 2014 19:17:39 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12730565.1406659711483.97472.1406920659485@arcas>
In-Reply-To: <JIRA.12730565.1406659711483@arcas>
References: <JIRA.12730565.1406659711483@arcas>
Subject: [jira] [Commented] (CASSANDRA-7638) Revisit GCInspector
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams commented on CASSANDRA-7638:
---------------------------------------------

bq. 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.

I agree, but it doesn't work on either 1.7.0_65-b17 or 1.8.0_11-b12 so there's not much point in having it.

> 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)