[
https://issues.apache.org/jira/browse/CASSANDRA-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118675#comment-13118675
]
Jonathan Ellis commented on CASSANDRA-3290:
-------------------------------------------
CASSANDRA-3289 would fit the description, except you should be seeing
AssertionErrors in the log if that were the case. Are you running a custom
script or did you otherwise turn off -ea, by chance?
> Upgrade from 0.7.9 to 1.0, the java stress tool gives "error reading key" on
> data created in 0.7.9
> --------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-3290
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3290
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0
> Reporter: Cathy Daw
> Assignee: Brandon Williams
> Fix For: 1.0.0
>
>
> *TEST CASE*
> * Install three node cluster with C* 0.7.9 with node1 as the seed
> * Run the 0.7.9 stress tool against node2,node3: ./stress -d node2,node3 -o
> insert
> * Run `nodetool -h node1 drain`
> * Upgrade binaries and edit cassandra.yaml for node1.
> * Startup C* 1.0 on node
> * Run the 0.7.9 stress tool against node2,node3: ./stress -d node2,node3 -o
> insert
> *ISSUE*
> * Run the 0.7.9 stress tool to read data: ./stress -d node2 -o read
> {code}
> cathy3:~/apache-cassandra-0.7.9-src/contrib/stress/bin# ./stress -d cathy3 -o
> read
> total,interval_op_rate,interval_key_rate,avg_latency,elapsed_time
> Operation [17] retried 10 times - error reading key 0521977
> Operation [9] retried 10 times - error reading key 0595365
> Operation [15] retried 10 times - error reading key 0513247
> {code}
> *Additional notes*
> * There are no errors in the log files
> * After upgrading the full ring, and running READ from both the old and new
> versions of stress tool, the error still exists
> * Once all nodes are upgraded, if I run INSERT followed by READ, the new
> reads are fine
--
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
