[CASSANDRA-8903] Super Columns exception during upgrade from C* 1.2.18 to C* 2.0.11

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Cannot Reproduce
• Severity: Normal
• Since Version: 2.0.11
• Assignee: Sylvain Lebresne
• Reporter: Erick Ramirez (deprecated)

Authors

Sylvain Lebresne

• Created: 04/Mar/15 07:05
• Updated: 16/Apr/19 09:31
• Resolved: 16/Aug/15 15:50

Description

While in the middle of an upgrade of a 12-node cluster, the following errors were constantly being reported in the logs:

ERROR [WRITE-/10.73.73.26] 2015-03-02 22:59:12,523 OutboundTcpConnection.java (line 234) error writing to /xx.xx.xx.xx 
java.lang.RuntimeException: Cannot convert filter to old super column format. Update all nodes to Cassandra 2.0 first. 
at org.apache.cassandra.db.SuperColumns.sliceFilterToSC(SuperColumns.java:353) 
at org.apache.cassandra.db.SuperColumns.filterToSC(SuperColumns.java:258) 
at org.apache.cassandra.db.RangeSliceCommandSerializer.serializedSize(RangeSliceCommand.java:284) 
at org.apache.cassandra.db.RangeSliceCommandSerializer.serializedSize(RangeSliceCommand.java:156) 
at org.apache.cassandra.net.MessageOut.serialize(MessageOut.java:116) 
at org.apache.cassandra.net.OutboundTcpConnection.writeInternal(OutboundTcpConnection.java:251) 
at org.apache.cassandra.net.OutboundTcpConnection.writeConnected(OutboundTcpConnection.java:203) 
at org.apache.cassandra.net.OutboundTcpConnection.run(OutboundTcpConnection.java:151)

Confirmed that code is accessing cluster via Thrift and not CQL API.

This issue is very similar to CASSANDRA-6966 but may relate to the way that single slice and reversed is being handled.

Issue Links

• is related to: CASSANDRA-14414 Errors in Supercolumn support in 2.0 upgrade