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

convenience workflow for replacing dead node

    Details

    • Type: Wish
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: 1.0.0
    • Component/s: Tools
    • Labels:
      None

      Description

      Replacing a dead node with a new one is a common operation, but "nodetool removetoken" followed by bootstrap is inefficient (re-replicating data first to the remaining nodes, then to the new one) and manually bootstrapping to a token "just less than" the old one's, followed by "nodetool removetoken" is slightly painful and prone to manual errors.

      First question: how would you expose this in our tool ecosystem? It needs to be a startup-time option to the new node, so it can't be nodetool, and messing with the config xml definitely takes the "convenience" out. A one-off -DreplaceToken=XXY argument?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                vijay2win@yahoo.com Vijay
                Reporter:
                jbellis Jonathan Ellis
                Reviewer:
                Nick Bailey
              • Votes:
                2 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 24h
                  24h
                  Remaining:
                  Remaining Estimate - 24h
                  24h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified