[ https://issues.apache.org/jira/browse/CASSANDRA-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100744#comment-13100744 ]
Chris Herron commented on CASSANDRA-3070: ----------------------------------------- I have seen something similar. I recently grew an 0.8.4 test cluster from N nodes to N*2 nodes. After running nodetool repair on each node, found that some counters were out of sync (counter values would vary reading from different hosts). > counter repair > -------------- > > Key: CASSANDRA-3070 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3070 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 0.8.4 > Reporter: ivan > Assignee: Sylvain Lebresne > Attachments: counter_local_quroum_maybeschedulerepairs.txt, > counter_local_quroum_maybeschedulerepairs_2.txt, > counter_local_quroum_maybeschedulerepairs_3.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: http://www.atlassian.com/software/jira