On 10.09.2013, at 02:34, "Laing, Michael" 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 of the SEDA
architect
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) c
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 wh
