cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12236) RTE from new CDC column breaks in flight queries.
Date Fri, 29 Jul 2016 07:59:20 GMT


Sylvain Lebresne commented on CASSANDRA-12236:

I fixed the unit test failures (mainly due to various minor errors in the change to {{RowUpdateBuilder}}
I did in the tests) in a new commit. There is 2 dtests failures for cqlsh DESCRIBE but that's
just because a consequence of this patch is that the {{cdc}} table properly won't be displayed
by DESCRIBE by default, which is imo fine. I have a trivial fix of that locally that I'll
push on commit. The rest of the dtest failures "seems" unrelated.

I seem to be have been able to start upgrade tests on that last branch which I include below,
but they haven't finished at the time of this writing so we'll see the results.

| [12236-trunk|] | [utests|]
| [dtests|] | [upgrade tests|]

> RTE from new CDC column breaks in flight queries.
> -------------------------------------------------
>                 Key: CASSANDRA-12236
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jeremiah Jordan
>            Assignee: Sylvain Lebresne
>             Fix For: 3.x
>         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
>       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

View raw message