[
https://issues.apache.org/jira/browse/CASSANDRA-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13480121#comment-13480121
]
Chris Herron commented on CASSANDRA-4417:
-----------------------------------------
Another observation since: in previous runs with key cache disabled we were not
seeing any errors. However I've since found some invalid counter shard errors
that are occurring during normal compaction.
{code}
ERROR [CompactionExecutor:6] 2012-10-19 15:43:50,920
org.apache.cassandra.db.context.CounterContext invalid counter shard detected;
(15b843e0-ff7c-11e0-0000-07f4b18563ff, 1, 1) and
(15b843e0-ff7c-11e0-0000-07f4b18563ff, 1, 2) differ only
in count; will pick highest to self-heal; this indicates a bug or corruption
generated a bad counter shard
{code}
So to be clear, this particular scenario is:
* C* 1.1.6 with key cache disabled.
* Load test ran earlier against this same setup; but no upgradesstables during
that run; no errors under load during that test run.
* Later, some nightly jobs ran that read from Super CF counters, write to other
CFs.
* Compaction activity occurs later after load test and nightly jobs complete.
Invalid counter shard errors are seen for some CFs. Gleaning from the log
output order, the affected CF's:
** *Did* have upgradesstables run upon them in previous configurations (1.1.6,
key cache on)
** Have not been written to at all for the purpose of the load test I've been
mentioning.
** Have been read from for these nightly jobs.
> 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
