cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Herron (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4417) invalid counter shard detected
Date Wed, 17 Oct 2012 23:54:03 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478505#comment-13478505
] 

Chris Herron commented on CASSANDRA-4417:
-----------------------------------------

bq. Probably, how was it deleted/recreated. Did you drop and recreate?

Yes, dropped (the schema migration flavor) and recreated a CF of the same name.

bq. Perform the same test without the upgradesstables part (i.e. only the writes and reads).
If so, does that change something?

Have already tested that scenario. Running this load test without the concurrent upgradesstables
compaction activity, the problem does not exhibit.

bq. during that test, is there anything involving streaming going on (a repair, a node bootstrapping/moving/decommissioning)?

Not that I know of. I can test again and monitor for streaming activity to see.

By the way, as we've been testing in preparation for a 1.1.x upgrade, we were seeing symptoms
of CASSANDRA-4571, CASSANDRA-4687 as well as this issue on C* 1.1.6. In investigating CASSANDRA-4687
we disabled key cache, repeated the load+upgradesstables test and these invalid counter shard
warnings did not appear.
                
> 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

Mime
View raw message