Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Won't Fix
-
None
-
None
-
Normal
Description
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