You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Daniel Meyer (JIRA)" <ji...@apache.org> on 2013/08/27 18:27:52 UTC
[jira] [Created] (CASSANDRA-5942) bootstrapping new node after
upgrading cluster causes counter columns to randomly have incorrect values
Daniel Meyer created CASSANDRA-5942:
---------------------------------------
Summary: 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
Fix For: 2.0
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira