incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alain RODRIGUEZ <arodr...@gmail.com>
Subject Re: Invalid Counter Shard errors?
Date Thu, 06 Sep 2012 10:51:35 GMT
Hi nobody knows about this ?

Alain

2012/9/3 Alain RODRIGUEZ <arodrime@gmail.com>

> Hello,
>
> I'm running a 1.1.2 Cassandra 2 nodes wide cluster with RF=2 (CL = 1,
> nodes are m1.large from Amazon).
>
> I had this error 524 times last month on the node 1 and 2805 time on
> the second node.
>
> Should I worry about it ? How can I fix these errors ?
>
> Alain
>
> 2012/6/2 Peter Schuller <peter.schuller@infidyne.com>:
> >> We're running a three node cluster of cassandra 1.1 servers, originally
> >> 1.0.7 and immediately after the upgrade the error logs of all three
> servers
> >> began filling up with the following message:
> >
> > The message you are receiving is new, but the problem it identifies is
> > not. The checking for this condition, and the logging, was added so
> > that certain kinds of counter corruption would be self-healed
> > eventually instead of remaining forever incorrect. Likely nothing is
> > wrong that wasn't before; you're just seeing it being logged now.
> >
> > And I can confirm having seen this on 1.1, so the root cause remains
> > unknown as far as I can tell (had previously hoped the root cause were
> > thread-unsafe shard merging, or one of the other counter related
> > issues fixed during the 0.8 run).
> >
> > --
> > / Peter Schuller (@scode, http://worldmodscode.wordpress.com)
>

Mime
View raw message