[
https://issues.apache.org/jira/browse/CASSANDRA-12236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384412#comment-15384412
]
Joshua McKenzie commented on CASSANDRA-12236:
---------------------------------------------
To clarify, this has nothing to do with CDC other than it being the first
feature that's changed system tables since 3.0 hit. In a post CASSANDRA-8099
world, the fact that we send across all system tables and reject queries with
unknown columns means that any changes to the system schema would cause this.
CDC just happens to be the first feature we've added since then that changes
schema.
Also - at the time that I added that message to NEWS.txt, from discussion
offline we didn't realize those exceptions would lead to internode
communication breaks.
> RTE from new CDC column breaks in flight queries.
> -------------------------------------------------
>
> Key: CASSANDRA-12236
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12236
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jeremiah Jordan
> Priority: Blocker
> Fix For: 3.8
>
>
> This RTE is not harmless. It will cause the internode connection to break
> which will cause all in flight requests between these nodes to die/timeout.
> {noformat}
> - Due to changes in schema migration handling and the storage format
> after 3.0, you will
> see error messages such as:
> "java.lang.RuntimeException: Unknown column cdc during
> deserialization"
> in your system logs on a mixed-version cluster during upgrades. This
> error message
> is harmless and due to the 3.8 nodes having cdc added to their schema
> tables while
> the <3.8 nodes do not. This message should cease once all nodes are
> upgraded to 3.8.
> As always, refrain from schema changes during cluster upgrades.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
