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

Make removetoken force always work

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 0.7.1
    • Legacy/Tools
    • None

    Description

      The 'removetoken force' command was intended for forcing a removal to complete when the removal stalls for some reason. The most likely reason being a streaming failure causing the node to wait forever for streams to complete.

      The command should be updated so that it can force a removal in any case. For example a node that was decommissioned but killed before a LEFT status was broadcasted. This leaves the node in a permanent 'leaving' state.

      Attachments

        1. 1900.txt
          1 kB
          Brandon Williams
        2. 1900-v2.txt
          2 kB
          Brandon Williams
        3. 1900-v3.txt
          2 kB
          Brandon Williams
        4. 1900-v4.txt
          3 kB
          Brandon Williams

        Activity

          People

            brandon.williams Brandon Williams
            nickmbailey Nick Bailey
            Brandon Williams
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

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