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 06:48:03 GMT


Sylvain Lebresne commented on CASSANDRA-4417:

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

Just to clarify, using batch commit log should only avoid the initial problem to reproduce
(assuming the analysis of the problem is correct of course). However, contrarily to what the
error message pretends, the existing "invalid counter shards" don't "heal" themselves as soon
a the message is logged. In fact, the message is logged each time we merge counter columns
that have conflicting shards and when that merge is triggered by a compaction, it will indeed
"heal" the shard. But we also merge each time we read for instance. In other words, even if
batch commit log fixes the problem, one will need to compact everything/wait for everything
to be compacted to have all logged messages disappear. Unless you've been able to reproduce
on a brand new cluster where the commit log was set to batch from the beginning (in which
case, if you have an easy way to reproduce, that would be interesting to know).

> 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