[ https://issues.apache.org/jira/browse/CASSANDRA-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407747#comment-13407747 ]
Peter Schuller commented on CASSANDRA-4417: ------------------------------------------- You are triggering a self-healing mechanism introduced in CASSANDRA-3641. I can confirm we're seeing it on 1.1 still too, even on sstables that haven't been upgraded from older versions. I don't think anyone knows exactly why it's happening. The condition being checked for is never supposed to happen. Prior to the CASSANDRA-3641 the result would be counters with values that never converge even with read-repair; post-CASSANDRA-3641 the values converge. But depending on the root cause, it's unclear whether there is a danger of incorrect counter values. > 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira