[
https://issues.apache.org/jira/browse/CASSANDRA-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485333#comment-13485333
]
Eric Lubow commented on CASSANDRA-4417:
---------------------------------------
We are getting this on DSE 2.2 (C* 1.1.5) on a new node during bootstrap. We
upgraded the cluster from C* 1.0.10 about 10 days ago and upgradesstables was
run on every node and we repaired the entire cluster. We ran We've been
getting this error sporadically on various nodes at various points but it's not
consistent. I've double and triple checked every node looking for sstable
files named "*-hd-*" and I don't see any (assuming that's enough to tell that
the sstable has been upgraded. If this error is an effect of requiring one to
run upgradesstables, then how would it happen during a bootstrap? All nodes
involved in this cluster are 1.1.5.
> 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
