[
https://issues.apache.org/jira/browse/CASSANDRA-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451823#comment-13451823
]
Fabien Rousseau commented on CASSANDRA-4417:
--------------------------------------------
Could it be that counter increment is written in commitlog and sent to other
replicas, BUT : commitlog is not yet flushed on disk AND cassandra is
stopped/killed.
Ex :
- node A receives an increment of 1 for c1
- it stores (A, 1, 1)
- it sends the increment to the replicas (A, 1, 1)
- node is killed (without commitog being flushed to disk)
- on restart, node A receives an increment of 3 for c1
- it stores (A, 1, 3) (because it has no way of knowing the clock "1" was
already attributed)
> 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
