cassandra-commits mailing list archives

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


Chris Herron commented on CASSANDRA-4417:

We are seeing large volumes of this error on all nodes when running a load test while also
running upgradesstables on multiple CF's on each node.

After reading Sylvain's comments above, tried running the same test with commitlog_sync: batch
- we get a similar volume of the same errors.

(Running a build from branch cassandra-1.1 at commit 4d2e5e73b127dc0b335176ddc1dec1f0244e7f6d,
with Java 6u35 on Amazon Linux 2.6.35)
> 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