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 743AE1032E for ; Tue, 1 Apr 2014 14:28:22 +0000 (UTC) Received: (qmail 34528 invoked by uid 500); 1 Apr 2014 14:28:20 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 34199 invoked by uid 500); 1 Apr 2014 14:28:18 -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 34170 invoked by uid 99); 1 Apr 2014 14:28:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2014 14:28:15 +0000 Date: Tue, 1 Apr 2014 14:28:15 +0000 (UTC) From: "Sylvain Lebresne (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-6966) Errors with Super Columns, mixup of 1.2 and 2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-6966?page=3Dcom.atla= ssian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-6966: ---------------------------------------- Attachment: 6966.txt We indeed had a bug (2 in fact) when translating internal filters to thrift= SC filters. Attaching a fix, and I've pushed [a dtest|https://github.com/r= iptano/cassandra-dtest/commit/7f24091e5ba4220d58649cd7e49e5403630ea646] for= this. > Errors with Super Columns, mixup of 1.2 and 2.0 > ----------------------------------------------- > > Key: CASSANDRA-6966 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6966 > Project: Cassandra > Issue Type: Bug > Reporter: Nicolas Lalev=C3=A9e > Assignee: Sylvain Lebresne > Fix For: 2.0.7 > > Attachments: 6966.txt > > > On our test cluster, we tried a upgrade of Cassandra from 1.2.11 to 2.0.6= . During the time we were running with 2 different versions of cassandra, t= here was errors in the logs: > ERROR [WRITE-/10.10.0.41] 2014-03-19 11:23:27,523 OutboundTcpConnection.j= ava (line 234) error writing to /10.10.0.41 > java.lang.RuntimeException: Cannot convert filter to old super column for= mat. Update all nodes to Cassandra 2.0 first. > at org.apache.cassandra.db.SuperColumns.sliceFilterToSC(SuperColum= ns.java:357) > at org.apache.cassandra.db.SuperColumns.filterToSC(SuperColumns.ja= va:258) > at org.apache.cassandra.db.ReadCommandSerializer.serializedSize(Re= adCommand.java:192) > at org.apache.cassandra.db.ReadCommandSerializer.serializedSize(Re= adCommand.java:134) > at org.apache.cassandra.net.MessageOut.serialize(MessageOut.java:1= 16) > at org.apache.cassandra.net.OutboundTcpConnection.writeInternal(Ou= tboundTcpConnection.java:251) > at org.apache.cassandra.net.OutboundTcpConnection.writeConnected(O= utboundTcpConnection.java:203) > at org.apache.cassandra.net.OutboundTcpConnection.run(OutboundTcpC= onnection.java:151) > I confirm we do have old style super columns which were designed when cas= sandra was 1.0.x. > Since in our test cluster the replication factor is 1, I can see errors o= n the client side, since 1 node among 2 was down. So I don't know for sure = if this error in cassandra affected the client, the time frame is too short= to be sure from the logs. -- This message was sent by Atlassian JIRA (v6.2#6252)