[ 
https://issues.apache.org/jira/browse/CASSANDRA-14841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677195#comment-16677195
 ] 

Ariel Weisberg commented on CASSANDRA-14841:
--------------------------------------------

Why would this block repairs and why would it stop you from monitoring repairs? 
Wouldn't you use nodetool repair admin to monitor repairs?

For repair it is just a history table. It's only populated after repair has 
already occurred.

I'm not sure users can alter the schema of the distributed system tables. 
@imaleksey is that actually possible?

> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to