[ https://issues.apache.org/jira/browse/CASSANDRA-18968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780532#comment-17780532 ]
Brandon Williams commented on CASSANDRA-18968: ---------------------------------------------- bq. this does not fail startup, it just unnecessarily emits a misleading warning. It's pretty harmless. Ah, I see, that explains why tests pass. bq. We could add a verbhandler to 3.x but at this stage I think it's easier/simpler to just version gate this feature I agree. > 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 > Priority: Normal > Labels: lhf > > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org