ssandra will now flush up to the two largest memtables to
> free up memory. Adjust flush_largest_memtables_at threshold in
> cassandra.yaml if you don't want Cassandra to do this automatically
>
> Feng Qu
> From: Jonathan Ellis
> To: user
> Cc: Feng Qu
> Sent: Frida
gt;To: user
>Cc: Feng Qu
>Sent: Friday, February 24, 2012 2:29 PM
>Subject: Re: nodetool ring runs very slow
>
>Read the server log and look for GCInspector output.
>
>On Fri, Feb 24, 2012 at 11:02 AM, Feng Qu wrote:
>> Hi Jonathan, how to check out whether it'
Haven't received any reply. Resend...
Feng Qu
>
> From: Feng Qu
>To: Cassandra User Group
>Sent: Wednesday, February 22, 2012 1:49 PM
>Subject: nodetool ring runs very slow
>
>
>We noticed that nodetool ring sometimes returns i
st node in a 6-node ring and it has opscenter
> community running on it.
>
> Feng Qu
>
>
> From: Jonathan Ellis
> To: user@cassandra.apache.org; Feng Qu
> Sent: Thursday, February 23, 2012 1:19 PM
> Subject: Re: nodetool ring runs very
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 wrote:
> We noticed that nodetool ring sometimes returns in 17-20 sec while it
> normally runs in less than a sec. Th
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
s
