[
https://issues.apache.org/jira/browse/CASSANDRA-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451240#comment-13451240
]
Peter Schuller commented on CASSANDRA-4417:
-------------------------------------------
I am not 100% certain, but I am fairly certain, that we've seen this on nodes
that haven't done any streaming whatsoever.
With respect to duplicates: It's certainly not *supposed* to happen. A given
counter shard, from a given node id, and with a given clock, should only ever
be produced exactly once by exactly one node. Obviously the bug isn't supposed
to happen to begin with, so that doesn't mean the bug isn't related to
streaming.
Hmmm.
Do you have a lot of writes normally? Is it possible that the correlation with
streaming is because of the fact that it initiates significant amounts of
compaction?
> 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
