Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-18968

StartupClusterConnectivityChecker fails on upgrade from 3.X

    XMLWordPrintableJSON

Details

    • Correctness - API / Semantic Implementation
    • Low
    • Low Hanging Fruit
    • User Report
    • All
    • None
    • Hide

      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.

      Show
      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.

    Description

      Starting up a new 4.X node on a 3.x cluster throws the following warning:

      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]}
      

      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.

      Attachments

        Issue Links

          Activity

            People

              isaacreath Isaac Reath
              paulo Paulo Motta
              Isaac Reath
              Paulo Motta, Stefan Miklosovic
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 2h 10m
                  2h 10m