cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: nodetool ring runs very slow
Date Fri, 24 Feb 2012 22:29:56 GMT
Read the server log and look for GCInspector output.

On Fri, Feb 24, 2012 at 11:02 AM, Feng Qu <mail4qf@gmail.com> wrote:
> Hi Jonathan, how to check out whether it's in GC storming? This server
> crashed few time due to Java heap out of memory. We use 8GB heap on a server
> with 96GB ram. This is first node in a 6-node ring and it has opscenter
> community running on it.
>
> Feng Qu
>
> ________________________________
> From: Jonathan Ellis <jbellis@gmail.com>
> To: user@cassandra.apache.org; Feng Qu <mail4qf@gmail.com>
> Sent: Thursday, February 23, 2012 1:19 PM
> Subject: Re: nodetool ring runs very slow
>
> The only time I've seen nodetool be that slow is when it was talking
> to a machine that was either swapping or deep into (JVM) GC storming.
>
> On Wed, Feb 22, 2012 at 3:49 PM, Feng Qu <mail4qf@gmail.com> wrote:
>> We noticed that nodetool ring sometimes returns in 17-20 sec while it
>> normally runs in less than a sec. There were some compaction running when
>> it
>> happened. Did compaction cause nodetool slowness? Anything else I should
>> check?
>>>>> time nodetool -h hostname ring
>> ....
>> real 0m17.595s
>> user 0m0.339s
>> sys 0m0.054s
>>
>> Feng Qu
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com
>
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Mime
View raw message