Jeremiah Jordan created CASSANDRA-5740:
------------------------------------------
Summary: Range scans fail during 1.0.12->1.2.6 rolling upgrade
Key: CASSANDRA-5740
URL: https://issues.apache.org/jira/browse/CASSANDRA-5740
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.0.12
Reporter: Jeremiah Jordan
Priority: Minor
While testing rolling upgrades, range scans that need to contact mixed version
nodes are failing mid upgrade.
N=3, RF=3
1 node 1.0.12
2 nodes 1.2.6
{noformat}
./cassandra-stress -e ALL --num-keys=1000 --operation=RANGE_SLICE
total,interval_op_rate,interval_key_rate,avg_latency,elapsed_time
0,0,0,NaN,10
0,0,0,NaN,20
0,0,0,NaN,30
0,0,0,NaN,40
0,0,0,NaN,50
0,0,0,NaN,60
./cassandra-stress -e ONE --num-keys=1000 --operation=RANGE_SLICE
total,interval_op_rate,interval_key_rate,avg_latency,elapsed_time
1000,100,500,0.030668,0
END
{noformat}
With N=3, RF=1 cassandra-cli "list" gives timeout exceptions as well:
{noformat}
cassandra-cli
Connected to: "Test Cluster" on 127.0.0.1/9160
Welcome to Cassandra CLI version 1.2.6
Type 'help;' or '?' for help.
Type 'quit;' or 'exit;' to quit.
default@unknown use Keyspace1 ;
Authenticated to keyspace: Keyspace1
default@Keyspace1 list Users ;
Using default limit of 100
Using default cell limit of 100
null
TimedOutException()
at
org.apache.cassandra.thrift.Cassandra$get_range_slices_result.read(Cassandra.java:12932)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
at
org.apache.cassandra.thrift.Cassandra$Client.recv_get_range_slices(Cassandra.java:734)
at
org.apache.cassandra.thrift.Cassandra$Client.get_range_slices(Cassandra.java:718)
at org.apache.cassandra.cli.CliClient.executeList(CliClient.java:1495)
at org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:279)
at
org.apache.cassandra.cli.CliMain.processStatementInteractive(CliMain.java:200)
at org.apache.cassandra.cli.CliMain.main(CliMain.java:327)
{noformat}
Upgrading through 1.1.X seems to fix the issue. Probably not worth changing
code, but should get a NEWS.txt entry or something.
--
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
