[
https://issues.apache.org/jira/browse/CASSANDRA-18968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780509#comment-17780509
]
Paulo Motta commented on CASSANDRA-18968:
-----------------------------------------
Hi [~brandon.williams] - this does not fail startup, it just unnecessarily
emits a misleading warning. It's pretty harmless.
I'm not familiar with this patch but I suspect 3.x nodes do not have the
{{PING_REQ}} message [sent
here|https://github.com/apache/cassandra/blob/f8c240147c307bf5c527ff3a34e3c0f3043b7e9c/src/java/org/apache/cassandra/net/StartupClusterConnectivityChecker.java#L143]
so the connectivity checker does not get the necessary number of
acknowledgements (3) to succeed.
If this is the case, I think the easiest fix is just to disable the check if
there are 3.X nodes, so the warning is not unnecessarily emitted.
> 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: [email protected]
For additional commands, e-mail: [email protected]
