[ https://issues.apache.org/jira/browse/CASSANDRA-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Velas updated CASSANDRA-4436: ----------------------------------- Attachment: (was: increments.cql.gz) > Counters in columns don't preserve correct values after cluster restart > ----------------------------------------------------------------------- > > Key: CASSANDRA-4436 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4436 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 1.0.10 > Reporter: Peter Velas > Attachments: increments.cql.gz > > > Similar to #3821. but affecting normal columns. > Set up a 2-node cluster with rf=2. > 1. Create a counter column family and increment a 100 keys in loop 5000 > times. > 2. Then make a rolling restart to cluster. > 3. Again increment another 5000 times. > 4. Make a rolling restart to cluster. > 5. Again increment another 5000 times. > 6. Make a rolling restart to cluster. > After step 6 we were able to reproduce bug with bad counter values. > Expected values were 15 000. Values returned from cluster are higher then > 15000 + some random number. > Rolling restarts are done with nodetool drain. Always waiting until second > node discover its down then kill java process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira