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

Avoid repairing already-repaired data by default

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Fix Version/s: 2.1 beta1
    • Component/s: None

      Description

      Repair has always built its merkle tree from all the data in a columnfamily, which is guaranteed to work but is inefficient.

      We can improve this by remembering which sstables have already been successfully repaired, and only repairing sstables new since the last repair. (This automatically makes CASSANDRA-3362 much less of a problem too.)

      The tricky part is, compaction will (if not taught otherwise) mix repaired data together with non-repaired. So we should segregate unrepaired sstables from the repaired ones.

        Attachments

        1. 5351_nodetool.log
          3 kB
          Lyuben Todorov
        2. 5351_node3.log
          308 kB
          Lyuben Todorov
        3. 5351_node2.log
          255 kB
          Lyuben Todorov
        4. 5351_node1.log
          230 kB
          Lyuben Todorov
        5. 0001-keep-repairedAt-time-when-scrubbing-and-no-bad-rows-.patch
          6 kB
          Marcus Eriksson
        6. 0001-Incremental-repair-wip.patch
          236 kB
          Marcus Eriksson

          Issue Links

            Activity

              People

              • Assignee:
                lyubent Lyuben Todorov
                Reporter:
                jbellis Jonathan Ellis
                Authors:
                Lyuben Todorov
                Reviewers:
                Marcus Eriksson
                Tester:
                Shawn Kumar
              • Votes:
                2 Vote for this issue
                Watchers:
                31 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: