Re: One node out of three not flushing memtables

2013-09-10 Thread Jan Algermissen
On 10.09.2013, at 02:34, Laing, Michael michael.la...@nytimes.com wrote: I have seen something similar. Of course correlation is not causation... Thanks for sharing - interesting. However, I still find it confusing that C* does not refuse service befor it dies. Maybe that is a by-product

One node out of three not flushing memtables

2013-09-09 Thread Jan Algermissen
I have a strange pattern: In a cluster with three equally dimensioned and configured nodes I keep loosing one because apparently it fails to flush its memtables: http://twitpic.com/dcrtel It is a different node every time. So far I understand that I should expect to see the chain-saw graph

Re: One node out of three not flushing memtables

2013-09-09 Thread Laing, Michael
I have seen something similar. Of course correlation is not causation... Like you, doing testing with heavy writes. I was using a python client to drive the writes using the cql module which is thrift based. The correlation I eventually tracked down was that whichever node my python client(s)