cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4417) invalid counter shard detected
Date Wed, 17 Oct 2012 19:10:03 GMT


Sylvain Lebresne commented on CASSANDRA-4417:

bq. Is that equivalent?

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

bq. This does reproduce for every test run.

Interesting, you may on something. Does it make sense for you to perform the same test without
the upgradesstables part (i.e. only the writes and reads). If so, does that change something?
Also, during that test, is there anything involving streaming going on (a repair, a node bootstrapping/moving/decommissioning)?
Trying to narrow down what's involved in you test.
> invalid counter shard detected 
> -------------------------------
>                 Key: CASSANDRA-4417
>                 URL:
>             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:

View raw message