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

Track repair state for more reliable repair

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsAdd voteVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

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

    Description

      During repair, coordinator and replica exchange various messages. I've seen cases that those messages sometimes get lost.
      We've made repair message to be more durable (CASSANDRA-5393, etc) but still messages seem to be lost and hang repair till messaging timeout reaches.

      We can prevent this by tracking repair status on repair participants, and periodically check state after certain period of times to make sure everything is working fine.

      We alse can add command / JMX API to query repair state.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            yukim Yuki Morishita Assign to me
            yukim Yuki Morishita
            Yuki Morishita

            Dates

              Created:
              Updated:

              Slack

                Issue deployment