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

Improve visibility into repair state

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Normal
    • Resolution: Unresolved
    • None
    • Consistency/Repair
    • None
    • Challenging

    Description

      Most of the repair flow is fire and forget, where we send a message, or start a job with a remote component, and then wait for a response of some type, or for the failure detector to tell us a node has died. This leaves several cases where the repair can hang, and operators have to guess about it’s state, and the best course of action. It would help if the state of a given repair could be polled, and possibly cancelled. This is going to involve touching the validation, anti-compaction, and streaming code.

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. CASSANDRA-15399 Add ability to track state in repair

          • Normal -
          • Resolved
          relates to

          Bug - A problem which impairs or prevents the functions of the product. CASSANDRA-13480 nodetool repair can hang forever if we lose the notification for the repair completing/failing

          • Low -
          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. CASSANDRA-14435 Diag. Events: JMX events

          • Normal -
          • Resolved

          Activity

            People

              Unassigned Unassigned
              bdeggleston Blake Eggleston
              Paulo Motta
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated: