Pedro Gordo created CASSANDRA-15804:
---------------------------------------

             Summary: system_schema keyspace complain of schema mismatch during 
upgrade
                 Key: CASSANDRA-15804
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15804
             Project: Cassandra
          Issue Type: Bug
            Reporter: Pedro Gordo


When upgrading from 3.11.4 to 3.11.6, we got the following error:

{code:Plain Text}
ERROR [MessagingService-Incoming-/10.20.11.59] 2020-05-07 13:53:52,627 
CassandraDaemon.java:228 - Exception in thread 
Thread[MessagingService-Incoming-/10.20.11.59,5,main]
java.lang.RuntimeException: Unknown column kind during deserialization
    at org.apache.cassandra.db.Columns$Serializer.deserialize(Columns.java:464) 
~[apache-cassandra-3.11.4.jar:3.11.4]
    at 
org.apache.cassandra.db.SerializationHeader$Serializer.deserializeForMessaging(SerializationHeader.java:419)
 ~[apache-cassandra-3.11.4.jar:3.11.4]
    at 
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.deserializeHeader(UnfilteredRowIteratorSerializer.java:195)
 ~[apache-cassandra-3.11.4.jar:3.11.4]
    at 
org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize30(PartitionUpdate.java:851)
 ~[apache-cassandra-3.11.4.jar:3.11.4]
    at 
org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize(PartitionUpdate.java:839)
 ~[apache-cassandra-3.11.4.jar:3.11.4]
    at 
org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:425)
 ~[apache-cassandra-3.11.4.jar:3.11.4]
    at 
org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:434)
 ~[apache-cassandra-3.11.4.jar:3.11.4]
    at 
org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:675)
 ~[apache-cassandra-3.11.4.jar:3.11.4]
    at 
org.apache.cassandra.service.MigrationManager$MigrationsSerializer.deserialize(MigrationManager.java:658)
 ~[apache-cassandra-3.11.4.jar:3.11.4]
    at org.apache.cassandra.net.MessageIn.read(MessageIn.java:123) 
~[apache-cassandra-3.11.4.jar:3.11.4]
    at 
org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:192)
 ~[apache-cassandra-3.11.4.jar:3.11.4]
    at 
org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:180)
 ~[apache-cassandra-3.11.4.jar:3.11.4]
    at 
org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:94)
 ~[apache-cassandra-3.11.4.jar:3.11.4]
{code}

I've noticed that system_schema.dropped_columns has a new column called "kind".
No issues arise from this error message, and the error disappeared after 
upgrading all nodes. But it still caused concerns due to the ERROR logging 
level, although "nodetool describecluster" reported only one schema version.

It makes sense for the system keyspaces to not be included for the 
"describecluster" schema version check, but it seems to me that these internal 
schema mismatches should be ignored if the versions are different between the 
nodes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to