Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-3290

Upgrade from 0.7.9 to 1.0, the java stress tool gives "error reading key" on data created in 0.7.9

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Not A Problem
    • 1.0.0
    • None
    • None
    • Normal

    Description

      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
        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 
        

      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

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            brandon.williams Brandon Williams Assign to me
            cdaw Cathy Daw
            Brandon Williams
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment