cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Resolved] (CASSANDRA-8903) Super Columns exception during upgrade from C* 1.2.18 to C* 2.0.11
Date Sun, 16 Aug 2015 15:50:45 GMT


Sylvain Lebresne resolved CASSANDRA-8903.
    Resolution: Cannot Reproduce

As said above, it's very unclear from the code of such exception could happen and with no
news on reproduction steps in 1+ month (and no additional report of this), closing as "Cannot

If you have more information to provide on this that would help reproducing/tracking this
down, feel free to reopen with said information. 

> Super Columns exception during upgrade from C* 1.2.18 to C* 2.0.11
> ------------------------------------------------------------------
>                 Key: CASSANDRA-8903
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Erick Ramirez
>            Assignee: Sylvain Lebresne
> While in the middle of an upgrade of a 12-node cluster, the following errors were constantly
being reported in the logs:
> {noformat}
> ERROR [WRITE-/] 2015-03-02 22:59:12,523 (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( 
> at org.apache.cassandra.db.SuperColumns.filterToSC( 
> at org.apache.cassandra.db.RangeSliceCommandSerializer.serializedSize(

> at org.apache.cassandra.db.RangeSliceCommandSerializer.serializedSize(

> at 
> at

> at

> at
> {noformat}
> 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.

This message was sent by Atlassian JIRA

View raw message