You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Isaac Reath (Jira)" <ji...@apache.org> on 2023/11/03 20:06:00 UTC

[jira] [Commented] (CASSANDRA-18968) StartupClusterConnectivityChecker fails on upgrade from 3.X

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

Isaac Reath commented on CASSANDRA-18968:
-----------------------------------------

Updated for 4.0 (https://github.com/apache/cassandra/pull/2863) and 4.1 (https://github.com/apache/cassandra/pull/2862)

> StartupClusterConnectivityChecker fails on upgrade from 3.X
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-18968
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18968
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local/Startup and Shutdown
>            Reporter: Paulo Motta
>            Assignee: Isaac Reath
>            Priority: Normal
>              Labels: lhf
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Starting up a new 4.X node on a 3.x cluster throws the following warning:
> {noformat}
> WARN  [main] 2023-10-27 15:58:22,234 StartupClusterConnectivityChecker.java:183 - Timed out after 10002 milliseconds, was waiting for remaining peers to connect: {dc1=[X.Y.Z.W, A.B.C.D]}
> {noformat}
> I think this is because the PING messages used by the startup check are not available on 3.X.
> To provide a smoother upgrade experience we should probably disable this check on a mixed version clusters, or skip peers on versions < 4.x when doing the connectivity check.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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