Cassandra
  1. Cassandra
  2. CASSANDRA-5104

new nodes should not attempt to bootstrap and stream until entire cluster is on the same major version

    Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Not a Problem
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None

      Description

      current behavior for bootstrapping nodes is for an exception to be thrown while a node attempts to stream from another node that has not had upgradesstables run yet.

      A node should not attempt to bootstrap into the cluster until the entire cluster is on the same major version and upgradesstables has already been run on every node in the ring.

        Issue Links

          Activity

          Jonathan Ellis made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Fix Version/s 2.0.1 [ 12324542 ]
          Resolution Not A Problem [ 8 ]
          Hide
          Jonathan Ellis added a comment -

          +1

          Show
          Jonathan Ellis added a comment - +1
          Hide
          Yuki Morishita added a comment -

          Now we have CASSANDRA-5772 in 2.0.0, can we '"won't fix" this?

          Show
          Yuki Morishita added a comment - Now we have CASSANDRA-5772 in 2.0.0, can we '"won't fix" this?
          Jonathan Ellis made changes -
          Fix Version/s 2.0.1 [ 12324542 ]
          Fix Version/s 2.0 [ 12324629 ]
          Yuki Morishita made changes -
          Link This issue is related to CASSANDRA-5772 [ CASSANDRA-5772 ]
          Jonathan Ellis made changes -
          Fix Version/s 2.0 [ 12324629 ]
          Fix Version/s 2.0 beta 1 [ 12322954 ]
          Hide
          Michael Kjellman added a comment -

          if the versions are compat, by all means it should be allowed, but it is equally as messy for the ned user in the middle of a upgrade currently. not saying this is the best solution, but the current one is not the best imho.

          Show
          Michael Kjellman added a comment - if the versions are compat, by all means it should be allowed, but it is equally as messy for the ned user in the middle of a upgrade currently. not saying this is the best solution, but the current one is not the best imho.
          Hide
          Jonathan Ellis added a comment -

          This sounds messy... There have been major versions that are streaming-compatible, and versions that didn't need upgradesstables. Those are rules of thumb, not iron laws.

          Show
          Jonathan Ellis added a comment - This sounds messy... There have been major versions that are streaming-compatible, and versions that didn't need upgradesstables. Those are rules of thumb, not iron laws.
          Gavin made changes -
          Workflow patch-available, re-open possible [ 12753583 ] reopen-resolved, no closed status, patch-avail, testing [ 12758825 ]
          Gavin made changes -
          Workflow no-reopen-closed, patch-avail [ 12744292 ] patch-available, re-open possible [ 12753583 ]
          Jonathan Ellis made changes -
          Field Original Value New Value
          Assignee Yuki Morishita [ yukim ]
          Fix Version/s 2.0 [ 12322954 ]
          Component/s Core [ 12312978 ]
          Michael Kjellman created issue -

            People

            • Assignee:
              Yuki Morishita
              Reporter:
              Michael Kjellman
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development