Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> GC and High CPU


Copy link to this message
-
Re: GC and High CPU
I think in our case we have a deadlock of not cleaning garbage in large
enough  chunks;  being stuck in high cpu is as good as being dead

Jack
On May 16, 2011 4:41 PM, "Andrew Purtell" <[EMAIL PROTECTED]> wrote:
> This is interesting because our "conventional wisdom" is those settings
should increase the chance of stop-the-world GC and should be avoided.
>
> - Andy
> (who always gets nervous when we start talking about GC black magic)
>
>> From: Jack Levin <[EMAIL PROTECTED]>
>> Subject: Re: GC and High CPU
>> To: [EMAIL PROTECTED]
>> Date: Monday, May 16, 2011, 5:06 PM
>>
>> Those are the lines I added:
>>
>> -XX:+CMSIncrementalMode \  <--------
>> -XX:+CMSIncrementalPacing \ <-------
>> -XX:-TraceClassUnloading <------
>>
>> -Jack
>> (used CMS before)
>>
>> On Mon, May 16, 2011 at 4:19 PM, Stack <[EMAIL PROTECTED]>
>> wrote:
>> > So, the change is that you started using CMS?  You
>> > were using the default GC previous?
>> >
>> > ParNew is much bigger now.
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB