[
https://issues.apache.org/jira/browse/CASSANDRA-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua McKenzie updated CASSANDRA-12026:
----------------------------------------
Fix Version/s: 3.8
> update NEWS.txt to explain system schema exceptions during partial cluster
> upgrade
> ----------------------------------------------------------------------------------
>
> Key: CASSANDRA-12026
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12026
> Project: Cassandra
> Issue Type: Bug
> Reporter: Russ Hatch
> Assignee: Joshua McKenzie
> Fix For: 3.8
>
> Attachments: 12026_v1.txt
>
>
> Upgrade tests found this exception occuring during upgrades:
> {noformat}
> node2: ERROR [MessagingService-Incoming-/127.0.0.1] 2016-06-16 20:14:59,268
> CassandraDaemon.java:217 - Exception in thread
> Thread[MessagingService-Incoming-/127.0.0.1,5,main]
> java.lang.RuntimeException: Unknown column cdc during deserialization
> at
> org.apache.cassandra.db.Columns$Serializer.deserialize(Columns.java:433)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.db.SerializationHeader$Serializer.deserializeForMessaging(SerializationHeader.java:407)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.deserializeHeader(UnfilteredRowIteratorSerializer.java:192)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize30(PartitionUpdate.java:668)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize(PartitionUpdate.java:656)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:341)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:350)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:610)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:593)
> ~[apache-cassandra-3.7.jar:3.7]
> at org.apache.cassandra.net.MessageIn.read(MessageIn.java:114)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:190)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:178)
> ~[apache-cassandra-3.7.jar:3.7]
> at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:92)
> ~[apache-cassandra-3.7.jar:3.7]
> {noformat}
> Which is apparently normal and should subside after full cluster upgrade to
> post-3.0 versions.
> NEWS.txt needs an update to let users know this is not a problem during their
> upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
