[
https://issues.apache.org/jira/browse/CASSANDRA-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457504#comment-13457504
]
Bartłomiej Romański commented on CASSANDRA-4417:
------------------------------------------------
Is it possible to predict how dangerous this bug could be? We are already
experiencing very serious problems with CASSANDRA-4639. Our counter values
suddenly became a few times higher than expected. As you can imagine this is a
disaster from the business point of view. We are already seriously thinking
about going back to SQL databases :/ I wonder how (if) this bug (and possible
other counter related bugs) can affect us. We rely heavily on counters.
Can this bug possibly lead to incorrect counter values? Temporarily or
permanently - will running repair fix it?
How incorrect counter values could be? Loosing a couple increments immediately
preceding a node failure is probably acceptable in most cases. Is it possible
to loose more increments? Or end up in completely incorrect counter values as
in CASSANDRA-4639?
What would exactly happen after hitting this bug. Running repair should fix it?
The "self-healing" mechanism would actually make counter consistent again? Or
we will get this error messages over and over?
Sorry for writing a comment full of questions, but I've got very limited
knowledge of cassandra internals. I'll be very thankful if someone could refer
to the questions above.
> invalid counter shard detected
> -------------------------------
>
> Key: CASSANDRA-4417
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4417
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.1
> Environment: Amazon Linux
> Reporter: Senthilvel Rangaswamy
>
> Seeing errors like these:
> 2012-07-06_07:00:27.22662 ERROR 07:00:27,226 invalid counter shard detected;
> (17bfd850-ac52-11e1-0000-6ecd0b5b61e7, 1, 13) and
> (17bfd850-ac52-11e1-0000-6ecd0b5b61e7, 1, 1) differ only in count; will pick
> highest to self-heal; this indicates a bug or corruption generated a bad
> counter shard
> What does it mean ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
