[CASSANDRA-3804] upgrade problems from 1.0 to trunk

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 1.1.0

Environment

ubuntu, cluster set up with ccm.

• Severity: Normal
• Assignee: Pavel Yaskevich
• Reporter: Tyler Patterson

Authors

Pavel Yaskevich

Reviewers

Sylvain Lebresne

• Created: 28/Jan/12 04:01
• Updated: 16/Apr/19 09:32
• Resolved: 23/Feb/12 17:10

Description

A 3-node cluster is on version 0.8.9, 1.0.6, or 1.0.7 and then one and only one node is taken down, upgraded to trunk, and started again. An rpc timeout exception happens if counter-add operations are done. It usually takes between 1 and 500 add operations before the failure occurs. The failure seems to happen sooner if the coordinator node is NOT the one that was upgraded. Here is the error:

======================================================================
ERROR: counter_upgrade_test.TestCounterUpgrade.counter_upgrade_test
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/nose/case.py", line 187, in runTest
    self.test(*self.arg)
  File "/home/tahooie/cassandra-dtest/counter_upgrade_test.py", line 50, in counter_upgrade_test
    cursor.execute("UPDATE counters SET row = row+1 where key='a'")
  File "/usr/local/lib/python2.7/dist-packages/cql/cursor.py", line 96, in execute
    raise cql.OperationalError("Request did not complete within rpc_timeout.")
OperationalError: Request did not complete within rpc_timeout.