cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3070) counter repair
Date Tue, 30 Aug 2011 11:23:37 GMT


Sylvain Lebresne commented on CASSANDRA-3070:

Because I don't know where the new debug messages were added, I'm not always sure what they
represents and  what to make of those logs. There is a counter context that seems odd in there,
and could explain the lack of synchronization, but the question is then more how this was
created in the first place.

If the sstables corresponding to that are not sensitive nor too huge and you can provide them,
I can offer to have a closer look. Short of that, knowing where the debug lines come from
may be of some help.

> counter repair
> --------------
>                 Key: CASSANDRA-3070
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8.4
>            Reporter: ivan
>            Assignee: Sylvain Lebresne
>         Attachments: counter_local_quroum_maybeschedulerepairs.txt
> Hi!
> We have some counters out of sync but repair doesn't sync values.
> We tried nodetool repair.
> We use LOCAL_QUORUM for read. A repair row mutation is sent to other nodes while reading
a bad row but counters wasn't repaired by mutation.
> Output of two nodes were uploaded. (Some new debug messages were added.)

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message