You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Chris Goffinet (JIRA)" <ji...@apache.org> on 2010/03/15 07:33:27 UTC
[jira] Commented: (CASSANDRA-896) GC issues with
LinkedBlockingQueue, very large heap sizes
[ https://issues.apache.org/jira/browse/CASSANDRA-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845198#action_12845198 ]
Chris Goffinet commented on CASSANDRA-896:
------------------------------------------
After waiting a bit, doing a Full GC actually worked as mentioned in above articles. Heap dropped to appropriate levels.
> GC issues with LinkedBlockingQueue, very large heap sizes
> ---------------------------------------------------------
>
> Key: CASSANDRA-896
> URL: https://issues.apache.org/jira/browse/CASSANDRA-896
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.6
> Reporter: Chris Goffinet
> Attachments: Screen shot 2010-03-14 at 10.19.09 PM.png, Screen shot 2010-03-14 at 10.20.31 PM.png
>
>
> We were doing a large import over thrift today (250M rows) with 50 columns each. We noticed when this process started, that the heap usage slowly began to rise. Eventually hitting 10GB. After investigating heap dumps we noticed this is linked to GC problems in the JVM for LinkedBlockingQueue. Sending a hint through jconsole to perform GC didn't help either.
> See this article:
> http://tech.puredanger.com/2009/02/11/linkedblockingqueue-garbagecollection/
> JDK 1.6.18 doesn't have this fix yet either. We could possibly add the change from:
> http://svn.apache.org/repos/asf/harmony/standard/classlib/trunk/modules/concurrent/src/main/java/java/util/concurrent/LinkedBlockingQueue.java
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.