[ https://issues.apache.org/jira/browse/CASSANDRA-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414315#comment-13414315 ]
Peter Velas commented on CASSANDRA-4436: ---------------------------------------- create keyspace test_old with placement_strategy = 'SimpleStrategy' and strategy_options = {replication_factor : 2} and durable_writes = true; use test_old; create column family cf1_increment with column_type = 'Standard' and comparator = 'BytesType' and default_validation_class = 'CounterColumnType' and key_validation_class = 'BytesType' and read_repair_chance = 1.0 and dclocal_read_repair_chance = 0.0 and gc_grace = 864000 and min_compaction_threshold = 4 and max_compaction_threshold = 32 and replicate_on_write = true and compaction_strategy = 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy' and caching = 'KEYS_ONLY' and compression_options = {'sstable_compression' : 'org.apache.cassandra.io.compress.SnappyCompressor'}; In version 1.0.10 am always able to reproduce with this steps.. but its not reproducible in 1.1.2 . When I stop writing and shutdown node with "nodetool drain" there are some small commitlog files, but I don't bother to delete them just restart cassandra process. Maybe this is case ? > 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 > > 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