[
https://issues.apache.org/jira/browse/CASSANDRA-12697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460947#comment-16460947
]
Gábor Auth commented on CASSANDRA-12697:
----------------------------------------
Hi guys,
I've tried to add a new DC to my cluster and I ran into a CDC bug via schema
disagreement between the old DCs and the new DC (with version 3.11.0)...
I've diffed the good and the bad system_scheme tables. The only difference is
the `cdc` field in three keyspaces (in `tables` and `views`):
- the value of `cdc` field on the good node is `False`
- the value of `cdc` field on the bad node is `null`
The value of `cdc` field on the other keyspaces is `null`. One or two years ago
I've tried the CDC feature but switched off... after I updated the schema of
the affected keyspaces on the new nodes with 'cdc=false' then everything is
okay.
> cdc column addition still breaks schema migration tasks
> -------------------------------------------------------
>
> Key: CASSANDRA-12697
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12697
> Project: Cassandra
> Issue Type: Bug
> Components: Distributed Metadata
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Major
> Fix For: 3.10
>
>
> This is a followup of CASSANDRA-12236, which basically didn't fully fix the
> problem. Namely, the fix from CASSANDRA-12236 skipped the {{cdc}} column in
> {{SchemaKeyspace.addTableParamsToRowBuilder()}}, but that method isn't used
> by schema "migration tasks" ({{MigrationRequestVerbHandler}}, which instead
> directly send the content of the full schema table it reads from disk. So we
> still end up with a RTE like CASSANDRA-12236.
--
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
