You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2019/01/02 17:57:00 UTC
[jira] [Updated] (CASSANDRA-14928) MigrationManager attempts to
pull schema from different major version nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-14928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benedict updated CASSANDRA-14928:
---------------------------------
Component/s: (was: 4.0)
> MigrationManager attempts to pull schema from different major version nodes
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-14928
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14928
> Project: Cassandra
> Issue Type: Bug
> Components: Distributed Metadata
> Reporter: Ariel Weisberg
> Assignee: Ariel Weisberg
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 4.0, 2.2.x, 3.0.x, 3.11.x
>
>
> MigrationManager will do the version check against nodes it hasn't connected to yet so it doesn't know their messaging service version. We should also check the version in gossip as an additional layer of protection.
> This causes many of the upgrade tests to fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org