[
https://issues.apache.org/jira/browse/CASSANDRA-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482370#comment-13482370
]
Sylvain Lebresne commented on CASSANDRA-4417:
---------------------------------------------
bq. No, sorry just happened to pick that example.
That's ok, thanks nonetheless.
I'm really starting to think that CASSANDRA-4071 is likely the main cause for
this and is very easy to reproduce in that case. The commit log we've discussed
earlier can also trigger that error, but it's probably much harder to trigger.
The good news is that as explained on the ticket, CASSANDRA-4071 won't corrupt
counters unless you are at RF=1 (in which case that's not a good news). The bad
one is I'm not really sure how to fix it.
> 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
