[jira] [Updated] (CASSANDRA-5724) Timeouts for slice/rangeslice queries while some nodes versions are lower than 1.2 and some higher.

["Ryan McGuire (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McGuire updated CASSANDRA-5724:
------------------------------------

    Labels: qa-resolved  (was: )

> Timeouts for slice/rangeslice queries while some nodes versions are lower than 1.2 and some higher.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5724
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5724
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2.0
>            Reporter: Or Sher
>            Assignee: Ryan McGuire
>              Labels: qa-resolved
>
> When doing a rolling upgrade from 1.0.* or 1.1.* to 1.2.* some slice or range slice queries executed against a 1.2.* node fails due to timeout exception:
> [default@orTestKS] list orTestCF;
> Using default limit of 100
> Using default column 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:1489)
> 	at org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:273)
> 	at org.apache.cassandra.cli.CliMain.processStatementInteractive(CliMain.java:210)
> 	at org.apache.cassandra.cli.CliMain.main(CliMain.java:337)
> It seems this issue is because of the new parameter in 1.2.*: internode_compression which is set to "all" by default.
> It seems that by setting this parameter to none solves the problem.
> I think the question is if Cassandra should support somehow nodes with different configuration for this parameter?



--
This message was sent by Atlassian JIRA
(v6.2#6252)