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

Sylvain Lebresne commented on CASSANDRA-12236:
----------------------------------------------

bq. Absolute most of them have been failing since before CDC AFAIK

I don't know. The test report for 3.7, which is 
[here|https://docs.google.com/document/d/16xfq7xeLuD93EVIery0VQLMHMkOfYp7wlyQ7cSg0xwI/edit#heading=h.a7qrmlkpqup2],
 pretends that not that long ago there was only 2 upgrade tests failures. Maybe 
it's not accurate, and I'll admit I'm a little skeptical of only 2 failures, 
but it would sound like we have add a big increase in those failures in the 
last 2 months. Doesn't prove at all that it's CDC related though.

> 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)

Reply via email to