cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xu Zhongxing (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13441) Schema version changes for each upgraded node in a rolling upgrade, causing migration storms
Date Fri, 07 Jul 2017 06:08:00 GMT

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

Xu Zhongxing commented on CASSANDRA-13441:
------------------------------------------

I still see this when a new node is joining the cluster. The cassandra version are all 3.11.0

ERROR [main] 2017-07-07 13:56:29,873 MigrationManager.java:172 - Migration task failed to
complete


> Schema version changes for each upgraded node in a rolling upgrade, causing migration
storms
> --------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-13441
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13441
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Distributed Metadata
>            Reporter: Jeff Jirsa
>            Assignee: Jeff Jirsa
>             Fix For: 3.0.14, 3.11.0, 4.0
>
>
> In versions < 3.0, during a rolling upgrade (say 2.0 -> 2.1), the first node to
upgrade to 2.1 would add the new tables, setting the new 2.1 version ID, and subsequently
upgraded hosts would settle on that version.
> When a 3.0 node upgrades and writes its own new-in-3.0 system tables, it'll write the
same tables that exist in the schema with brand new timestamps. As written, this will cause
all nodes in the cluster to change schema (to the version with the newest timestamp). On a
sufficiently large cluster with a non-trivial schema, this could cause (literally) millions
of migration tasks to needlessly bounce across the cluster.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message