[
https://issues.apache.org/jira/browse/CASSANDRA-18968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isaac Reath updated CASSANDRA-18968:
------------------------------------
Test and Documentation Plan:
In this scenario you should see:
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]}.
After applying this patch, instead you should see:
Skipping startup connectivity check as some nodes may be running Cassandra
version 3 or older which does not support connectivity checking.
Status: Patch Available (was: Open)
> 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: [email protected]
For additional commands, e-mail: [email protected]
