nc.com]
Sent: Monday, July 01, 2013 2:48 PM
To: user@cassandra.apache.org
Subject: RE: about FlushWriter "All time blocked"
Thanks guys, these sound like good suggestions, will try those out.
Aaron, we have around 80 CFs.
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: Fri
Thanks guys, these sound like good suggestions, will try those out.
Aaron, we have around 80 CFs.
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: Friday, June 28, 2013 10:05 PM
To: user@cassandra.apache.org
Subject: Re: about FlushWriter "All time blocked"
We do not use
0
>> InternalResponseStage 0 0 43 0
>> 0
>> HintedHandoff 0 0 3 0
>> 0
>>
>> Thanks,
>> Arindam
>>
>> -Original
iver0 0 0 0
> 0
> InternalResponseStage 0 0 43 0
> 0
> HintedHandoff 0 0 3 0
> 0
>
> Thanks,
> Arindam
M
To: user@cassandra.apache.org
Subject: Re: about FlushWriter "All time blocked"
> FlushWriter 0 0191 0
> 12
This means there were 12 times the code wanted to put an memtable in the queue
to be flushed to disk but
: aaron morton [mailto:aa...@thelastpickle.com]
发送时间: 2013年6月26日 13:29
收件人: user@cassandra.apache.org
主题: Re: about FlushWriter "All time blocked"
> FlushWriter 0 0191 0
> 12
This means there were 12 times the code want
> FlushWriter 0 0191 0
> 12
This means there were 12 times the code wanted to put an memtable in the queue
to be flushed to disk but the queue was full.
The length of this queue is controlled by the memtable_flush_queue_size
htt
3 node
cent os
CPU 8core memory 32GB
cassandra 1.2.5
my scenario: many counter incr, every node has one client program, performance
is 400 wps /every clicent (it’s so slowly)
my question：
Ø nodetool tpstats
-
Pool NameActive Pending Com
