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

gossip and tokenMetadata get hostId out of sync on failed replace_node with the same IP address

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: 1.2.11, 2.0.2
    • Component/s: None
    • Labels:
      None

      Description

      If you try to replace_node an existing, live hostId, it will error out. However if you're using an existing IP to do this (as in, you chose the wrong uuid to replace on accident) then the newly generated hostId wipes out the old one in TMD, and when you do try to replace it replace_node will complain it does not exist. Examination of gossipinfo still shows the old hostId, however now you can't replace it either.

        Attachments

        1. 5916.txt
          17 kB
          Brandon Williams
        2. 5916-v2.txt
          19 kB
          Brandon Williams
        3. 5916-v3.txt
          20 kB
          Brandon Williams
        4. 5916-v4.txt
          21 kB
          Brandon Williams

          Issue Links

            Activity

              People

              • Assignee:
                brandon.williams Brandon Williams
                Reporter:
                brandon.williams Brandon Williams
                Reviewer:
                Tyler Hobbs
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: