[
https://issues.apache.org/jira/browse/CASSANDRA-13274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15885919#comment-15885919
]
Robert Stupp commented on CASSANDRA-13274:
------------------------------------------
CASSANDRA-11138 sets the messaging-version for any node to {{Math.min(version,
current_version}}. I.e. a newer node (aka C*4.0 using messaging-version 11)
would appear as messaging-version 10 in 3.* nodes. That basically allows
migration-tasks (schema pull/push) between different messaging versions.
> Fix rolling upgrade to 4.0+
> ---------------------------
>
> Key: CASSANDRA-13274
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13274
> Project: Cassandra
> Issue Type: Bug
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Priority: Critical
> Fix For: 3.0.x, 3.11.x
>
>
> A rolling upgrade from 3.* to 4.0 (messaging version {{11}}) unveils a
> regression caused by CASSANDRA-11128.
> Generally, we store all possible options/attributes including the default
> values in the schema. This causes (expected) schema-version-mismatches during
> rolling upgrades and therefore we prevent schema pulls/pushes in this
> situation, which has been broken by CASSANDRA-11128.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
