[
https://issues.apache.org/jira/browse/CASSANDRA-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450766#comment-13450766
]
Charles Brophy edited comment on CASSANDRA-4417 at 9/8/12 3:39 AM:
-------------------------------------------------------------------
We have a six node cluster [1.1.3, jdk 1.6.33, CentOs 6] with even key range
balance, random partitioner, and with replication factor=2. I get these errors
immediately following running "nodetool repair" but ONLY if a streaming repair
happens as a result. We are serving live updates to our counters from our
clickstream. My guess is that the sstable being streamed between the servers
winds up becoming "out of date" for the duration of the streaming process and
ends up containing these "duplicates" that are vetted during the subsequent
compaction. In any case, for us it is 100% reproducible via: nodetool repair ->
streaming repair -> subsequent compaction. Let me know if you need more
details. Hope this helps!
was (Author: charlesb_zulily):
We have a six node cluster with even key range balance, random partitioner,
and with replication factor=2. I get these errors immediately following running
"nodetool repair" but ONLY if a streaming repair happens as a result. We are
serving live updates to our counters from our clickstream. My guess is that the
sstable being streamed between the servers winds up becoming "out of date" for
the duration of the streaming process and ends up containing these "duplicates"
that are vetted during the subsequent compaction. In any case, for us it is
100% reproducible via: nodetool repair -> streaming repair -> subsequent
compaction. Let me know if you need more details. Hope this helps!
> 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
