[
https://issues.apache.org/jira/browse/CASSANDRA-14841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676671#comment-16676671
]
Tommy Stendahl commented on CASSANDRA-14841:
--------------------------------------------
I think there is another scenario we have to consider, if we have several DC's
its possible to do repair with in one dc and we would only need the nodes
within that DC to be on the same version, if there are another version in
another DC it should not be a problem.
And its also possible to create the new columns manually before starting the
upgrade, in this case both reads and writes will work.
So just blocking the writes while having mixed versions might not be so good.
Its only in the DC I'm currently upgrading that I can't run repairs but I would
not be able to monitor the repair status in DC's with the new version.
I think we should make it possible to override the blocking with some
configuration so you can decide to write repair history despite having mixed
versions. Or remove the blocking of writes and document in the NEWS.txt how to
create the new columns before starting to upgrade.
> Don't write to system_distributed.repair_history, system_traces.sessions,
> system_traces.events in mixed version 3.X/4.0 clusters
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-14841
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14841
> Project: Cassandra
> Issue Type: Bug
> Reporter: Tommy Stendahl
> Assignee: Ariel Weisberg
> Priority: Major
> Fix For: 4.0
>
>
> 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-/10.216.193.244] CassandraDaemon.java:228
> Exception in thread Thread[MessagingService-Incoming-/10.216.193.244,5,main]
> java.lang.RuntimeException: Unknown column coordinator_port during
> deserialization
> at org.apache.cassandra.db.Columns$Serializer.deserialize(Columns.java:452)
> ~[apache-cassandra-3.11.3.jar:3.11.3]
> at
> org.apache.cassandra.db.filter.ColumnFilter$Serializer.deserialize(ColumnFilter.java:482)
> ~[apache-cassandra-3.11.3.jar:3.11.3]
> at
> org.apache.cassandra.db.ReadCommand$Serializer.deserialize(ReadCommand.java:760)
> ~[apache-cassandra-3.11.3.jar:3.11.3]
> at
> org.apache.cassandra.db.ReadCommand$Serializer.deserialize(ReadCommand.java:697)
> ~[apache-cassandra-3.11.3.jar:3.11.3]
> at
> org.apache.cassandra.io.ForwardingVersionedSerializer.deserialize(ForwardingVersionedSerializer.java:50)
> ~[apache-cassandra-3.11.3.jar:3.11.3]
> at org.apache.cassandra.net.MessageIn.read(MessageIn.java:123)
> ~[apache-cassandra-3.11.3.jar:3.11.3]
> at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:192)
> ~[apache-cassandra-3.11.3.jar:3.11.3]
> at
> org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:180)
> ~[apache-cassandra-3.11.3.jar:3.11.3]
> at
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:94)
> ~[apache-cassandra-3.11.3.jar:3.11.3]{noformat}
> I think it was introduced by CASSANDRA-7544.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
