[
https://issues.apache.org/jira/browse/CASSANDRA-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482552#comment-13482552
]
Chris Herron commented on CASSANDRA-4417:
-----------------------------------------
bq. I'm really starting to think that CASSANDRA-4071 is likely the main cause
for this and is very easy to reproduce in that case. The commit log we've
discussed earlier can also trigger that error, but it's probably much harder to
trigger.
In our case:
* We haven't made any topology changes
* Our test drops and recreates the affected CFs. No nodes die during the test
(w.r.t. unclean shutdown and commit log)
* After previous load test runs under different configuration (see below), no
nodes die, and we use nodetool drain before restarting with updated configs.
Note my earlier comment above I said:
bq. In investigating CASSANDRA-4687 we disabled key cache, repeated the
load+upgradesstables test and these invalid counter shard warnings did not
appear.
Given that we don't have a topology change, can you think of a scenario where a
commitlog issue is still contributing?
> 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
