RE: about FlushWriter "All time blocked"

2013-10-17 Thread Arindam Barua
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

RE: about FlushWriter "All time blocked"

2013-07-01 Thread Arindam Barua
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

Re: about FlushWriter "All time blocked"

2013-06-28 Thread aaron morton
0 >> InternalResponseStage 0 0 43 0 >> 0 >> HintedHandoff 0 0 3 0 >> 0 >> >> Thanks, >> Arindam >> >> -Original

Re: about FlushWriter "All time blocked"

2013-06-27 Thread Nate McCall
iver0 0 0 0 > 0 > InternalResponseStage 0 0 43 0 > 0 > HintedHandoff 0 0 3 0 > 0 > > Thanks, > Arindam

RE: about FlushWriter "All time blocked"

2013-06-27 Thread Arindam Barua
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

Re: about FlushWriter "All time blocked"

2013-06-25 Thread aaron morton
> 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