[
https://issues.apache.org/jira/browse/CASSANDRA-12236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405884#comment-15405884
]
Joshua McKenzie commented on CASSANDRA-12236:
---------------------------------------------
bq. Doesn't prove at all that it's CDC related though
In the context of this discussion here, I'm less concerned about the immediate
root-causing and more concerned about:
bq. it will take a while to address them (likely not before 3.10).
I don't think we should be in the habit of cutting releases with failing
upgrade tests.
I had [~philipthompson] attempt an upgrade test run against the SHA right
before CDC with results
[here|http://cassci.datastax.com/view/Dev/view/josh-mckenzie/job/josh-mckenzie-upgrade_pre_cdc_3.8-upgrade/8/#showFailuresLink].
22 failures on that SHA, so the upgrade tests weren't in a good place even
before this schema-propagation issue.
Given the paging failures (potentially CASSANDRA-10848/CASSANDRA-10730 related)
and the failures we already had going into this commit, I think we've just had
multiple fairly large upgrade test regressions during the 3.8 time window that
we're just going to have to grind through.
> 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
> Assignee: Sylvain Lebresne
> Fix For: 3.8, 3.9
>
> Attachments: 12236.txt
>
>
> 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)
