I ran the same cql query against my 3 nodes (after adding the third and
repairing each of them):
On the new node:
cqlsh:mykeyspace> select '20121029#myevent' from 'mycf' where key =
'887#day';
20121029#myevent
---
4983
On the 2 others (old nodes):
cqlsh:mykeyspac
"Can you try it thought, or run a repair ?"
Repairing didn't help
"My first thought is to use QUOURM"
This fix the problem. However, my data is probably still inconsistent, even
if I read now always the same value. The point is that I can't handle a
crash with CL.QUORUM, I can't even restart a n
> "What CL are you using ?"
>
> I think this can be what causes the issue. I'm writing and reading at CL ONE.
> I didn't drain before stopping Cassandra and this may have produce a fail in
> the current counters (those which were being written when I stopped a server).
My first thought is to use
"What version of cassandra are you using ?"
1.1.2
"Can you explain this further?"
I had an unexplained amount of reads (up to 1800 r/s and 90 Mo/s) on one
server the other was doing about 200 r/s and 5 Mo/s max. I fixed it by
rebooting the server. This server is dedicated to cassandra. I can't t
What version of cassandra are you using ?
> I finally restart Cassandra. It didn't solve the problem so I stopped
> Cassandra again on that node and restart my ec2 server. This solved the issue
> (1800 r/s to 100 r/s).
Can you explain this further?
Was something writing to the cluster ?
Did you
maybe enable the debug in log4j-server.properties and going through the log
to see what actually happen?
On Tue, Oct 30, 2012 at 7:31 PM, Alain RODRIGUEZ wrote:
> Hi,
>
> I have an issue with counters, yesterday I had a lot of ununderstandable
> reads/sec on one server. I finally restart Cassand
