[ https://issues.apache.org/jira/browse/CASSANDRA-7638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081482#comment-14081482 ]
Brandon Williams commented on CASSANDRA-7638: --------------------------------------------- Interesting. It seems to work just as well as the old way, though we could probably get rid of cause because that always says 'No GC': {noformat} INFO 21:16:29 GC for ConcurrentMarkSweep caused by No GC in 5282ms(start:65641, end:70923):["Par Eden Space" 1106824 -> 52309680 (214827008)]["CMS Old Gen" 616303848 -> 307287104 (805306368)]["CMS Perm Gen" 28911208 -> 28906672 (85983232)]["Code Cache" 4652992 -> 4657984 (50331648)] max: 1183252480 {noformat} Good info besides that, though. > 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)