cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Schuller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4417) invalid counter shard detected
Date Wed, 12 Sep 2012 07:09:09 GMT

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

Peter Schuller commented on CASSANDRA-4417:
-------------------------------------------

@Sylvain I know it wouldn't be correlated with the *same* node; I was referring to uncontrolled
shutdowns in general in the cluster.

@Omid: Presumably the premise was that the mutation goes through the commit log on the leader
prior to replication. I'm not sure if this is the case, but if it is, then it should work.

@jbellis FWIW, our counter use-cases are such that going commit log synch is probably not
feasable due to very high write throughput. Doesn't mean other people's use-cases are the
same, and of course I *fully* support the idea of being correct by default (as opposed to
performant by default).

@Sylvain again: I agree about refreshing nodeid on every unclean restart being potentially
dangerous. Counters are already huge due to the size of counter shards, and refreshing nodeids
in any situation which might result in en-masse refreshment can definitely be dangerous both
from a CPU usage perspective as well as a disk space one.
                
> 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