hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kihwal Lee <kih...@yahoo-inc.com>
Subject Re: Suspected memory leak
Date Thu, 01 Dec 2011 20:20:18 GMT
Adding to the excellent write-up by Jonathan:
Since finalizer is involved, it takes two GC cycles to collect them.  Due to a bug/bugs in
the CMS GC, collection may not happen and the heap can grow really big.  See http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7112034
for details.

Koji tried "-XX:-CMSConcurrentMTEnabled" and confirmed that all the socket related objects
were being collected properly. This option forces the concurrent marker to be one thread.
This was for HDFS, but I think the same applies here.


On 12/1/11 1:26 PM, "Stack" <stack@duboce.net> wrote:

Make sure its not the issue that Jonathan Payne identifiied a while
back: https://groups.google.com/group/asynchbase/browse_thread/thread/c45bc7ba788b2357#

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message