Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B8D521097B for ; Thu, 4 Jul 2013 17:05:50 +0000 (UTC) Received: (qmail 82295 invoked by uid 500); 4 Jul 2013 17:05:49 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 82237 invoked by uid 500); 4 Jul 2013 17:05:49 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 82222 invoked by uid 99); 4 Jul 2013 17:05:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jul 2013 17:05:48 +0000 Date: Thu, 4 Jul 2013 17:05:48 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-5724) Timeouts for slice/rangeslice queries while some nodes versions are lower than 1.2 and some higher. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5724: -------------------------------------- Assignee: Ryan McGuire Can we reproduce? There is already code to special case "never use compression when speaking to a 1.1 node." > 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 > > 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 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