[jira] [Issue Comment Deleted] (CASSANDRA-5942) bootstrapping new node after upgrading cluster causes counter columns to randomly have incorrect values

["Tom Lin (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-5942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Lin updated CASSANDRA-5942:
-------------------------------
    Comment: was deleted

(was: Is there a fix for this issue yet?I recently upgrade my 3-node cluster from 1.2.6 to 2.0.0 and I found some counter columns value has changed. Please see followed diff, there are three rows has the incorrect value. quota is the counter column:

21c21
< Row(user_id=u'ba9bec6495f4acb33461ab5b0a44dcff094a0151771c53d62a4875d733b61fae', collections=None, quota=-120)
---
> Row(user_id=u'ba9bec6495f4acb33461ab5b0a44dcff094a0151771c53d62a4875d733b61fae', collections=None, quota=640)
254c254
< Row(user_id=u'757cf2128a4eb2ebbf6c7ebcccc9c85861a1a9d3f2727b6dddffd399723fd518', collections=None, quota=-1745)
---
> Row(user_id=u'757cf2128a4eb2ebbf6c7ebcccc9c85861a1a9d3f2727b6dddffd399723fd518', collections=None, quota=4307086)
261c261
< Row(user_id=u'0eaa4cf27acea7604902551551fe9518a1d4c6d92122908b6172cc0a9c397307', collections=None, quota=-25207921)
---
> Row(user_id=u'0eaa4cf27acea7604902551551fe9518a1d4c6d92122908b6172cc0a9c397307', collections=None, quota=-33590770))

> bootstrapping new node after upgrading cluster causes counter columns to randomly have incorrect values
> -------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5942
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5942
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: java version "1.7.0_25"
> Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
>            Reporter: Daniel Meyer
>            Assignee: Russ Hatch
>         Attachments: logs.tar, upgrade_through_versions_test.py
>
>
> Running the latest version of upgrade_through_versions_test will randomly fail at a rate of about 1 out of 5 runs due to an incorrect counter value.  A slightly modified version of the test is attached for reference.  This version has trunk eliminated from the versions list and an extra debugging statement.
> The problem occurs after upgrading to the 2.0 branch from the 1.2 branch and after boostrapping a new node to the cluster.  Best way to repro is just run the test in a loop 5 to 10 times. 
> Be sure to set PRINT_DEBUG env variable to true and run test with --nocapture to see the debug output.  Logs are also included.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)