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

Don't mark sstables as repairing when doing sub range repair

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Severity:
      Normal

      Description

      Since CASSANDRA-10422 we don't do anticompaction when a user issues a sub range repair (-st X -et Y), but we still mark sstables as repairing.

      We should avoid marking them as users might want to run many sub range repair sessions in parallel.

      The reason we mark sstables is that we don't want another repair session to steal the sstables before we do anticompaction, and since we do no anticompaction with sub range repair we have no benefit from the marking.

        Attachments

          Activity

          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

            • Assignee:
              marcuse Marcus Eriksson Assign to me
              Reporter:
              marcuse Marcus Eriksson
              Authors:
              Marcus Eriksson
              Reviewers:
              Yuki Morishita

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment