I don't understand what the three in parentheses values are exactly. I guess
the last number is the count and the middle one is the number of increments,
is that true ? What is the first string (identical in all the errors) ?
It's (UUID, clock, increment). Very briefly, counter columns in
The significance I think is: If it is indeed the case that the higher
value is always *in fact* correct, I think that's inconsistent with
the hypothesis that unclean shutdown is the sole cause of these
problems - as long as the client is truly submitting non-idempotent
counter increments without a
I think that's inconsistent with the hypothesis that unclean shutdown is
the sole cause of these problems
I agree, we just never shut down any node, neither had any crash, and yet
we have these bugs.
About your side note :
We know about it, but we couldn't find any other way to be able to
I would like to understand or do my best helping you to understand this
issue.
I got the following (shortened) logs:
(03a227f0-a5c3-11e1--b7f5e49dceff, 3, 3) and
(03a227f0-a5c3-11e1--b7f5e49dceff, 3, 0)
(03a227f0-a5c3-11e1--b7f5e49dceff, 6, 6) and
This problem is not new to 1.1
That's what I understood from your last comment.
Is there a way to fix this error ? What is its impact on my data ?
Alain
2012/9/7 Peter Schuller peter.schul...@infidyne.com
This problem is not new to 1.1.
On Sep 6, 2012 5:51 AM, Radim Kolar h...@filez.com
Is there a way to fix this error ? What is its impact on my data ?
The fact that the message shows means that Cassandra has attempted to
repair the problem so there isn't much to do. However the fact that
you do get the messages in the first means that there is a bug
somewhere that generate
I have a very reliable repro case on our cluster involving nodetool repair.
I posted a summary in a comment on the issue. Let me know if more details
are needed.
Charles
On Fri, Sep 7, 2012 at 8:35 AM, Sylvain Lebresne sylv...@datastax.comwrote:
Is there a way to fix this error ? What is its
Hi nobody knows about this ?
Alain
2012/9/3 Alain RODRIGUEZ arodr...@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
i would migrate to 1.0 because 1.1 is highly unstable.
This problem is not new to 1.1.
On Sep 6, 2012 5:51 AM, Radim Kolar h...@filez.com wrote:
i would migrate to 1.0 because 1.1 is highly unstable.
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
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
Ok, will do. Thanks for the reply.
C
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Invalid-Counter-Shard-errors-tp7580163p7580189.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
Hi guys,
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:
ERROR [ReplicateOnWriteStage:177] 2012-05-31 08:17:02,236
CounterContext.java (line 381)
I suggest creating a ticket on https://issues.apache.org/jira/browse/CASSANDRA
with the details.
If it is an immediate concern see if you can find someone in the #cassandra
chat room http://cassandra.apache.org/
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
15 matches
Mail list logo
