Currently on 2.1.6 I'm seeing behavior like the following: cqlsh:walker> select * from counter_table where field = 'test'; field | value -------+------- test | 30 (1 rows) cqlsh:walker> select * from counter_table where field = 'test'; field | value -------+------- test | 90 (1 rows) cqlsh:walker> select * from counter_table where field = 'test'; field | value -------+------- test | 30 (1 rows)
Using tracing I can see that one node has wrong data. However running repair on this table does not seem to have done anything, I still see the wrong value returned from this same node. Potentially relevant facts: - Recently upgraded to 2.1.6 from 2.0.14 - This table has ~million rows, low contention, and fairly high increment rate Mainly wondering: - Is this known or expected? I know Cassandra counters have had issues but thought by now it should be able to keep a consistent counter or at least repair it... - Any way to "reset" this counter? - Any other stuff I can check?
