cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tommy Stendahl (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-14841) Unknown column coordinator_port during deserialization
Date Thu, 01 Nov 2018 15:14:00 GMT


Tommy Stendahl commented on CASSANDRA-14841:

Maybe I'm just picky. I agree we can't run repair in mixed version but does that mean I should
not read repair history?

Will this be an issue? Maybe not. In our case we have a system for monitoring the status of
the cluster which among other things reads from the repair history but I guess we could make
it possible to disable that during upgrade. Monitoring the state of repairs while having mixed
versions doesn't make much sens anyway.

> Unknown column coordinator_port during deserialization
> ------------------------------------------------------
>                 Key: CASSANDRA-14841
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Tommy Stendahl
>            Assignee: Ariel Weisberg
>            Priority: Major
> When upgrading from 3.x to 4.0 I get exceptions in the old nodes once the first 4.0 node
starts up. I have tested to upgrade from both 3.0.15 and 3.11.3 and get the same problem.
> {noformat}
> 2018-10-22T11:12:05.060+0200 ERROR [MessagingService-Incoming-/]
Exception in thread Thread[MessagingService-Incoming-/,5,main]
> java.lang.RuntimeException: Unknown column coordinator_port during deserialization
> at org.apache.cassandra.db.Columns$Serializer.deserialize( ~[apache-cassandra-3.11.3.jar:3.11.3]
> at org.apache.cassandra.db.filter.ColumnFilter$Serializer.deserialize(
> at org.apache.cassandra.db.ReadCommand$Serializer.deserialize( ~[apache-cassandra-3.11.3.jar:3.11.3]
> at org.apache.cassandra.db.ReadCommand$Serializer.deserialize( ~[apache-cassandra-3.11.3.jar:3.11.3]
> at
> at ~[apache-cassandra-3.11.3.jar:3.11.3]
> at
> at
> at
> I think it was introduced by CASSANDRA-7544.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message