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

PendingAntiCompaction should be more judicious in the compactions it cancels

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Fix Version/s: 4.0
    • Component/s: Local/Compaction
    • Labels:
      None
    • Change Category:
      Performance
    • Complexity:
      Challenging

      Description

      PendingAntiCompaction currently cancels all ongoing compactions to be able to grab the sstables it requires - it should;

      • avoid stopping ongoing anticompactions - for example, if we have an sstable [0, 100] and are anticompacting it on [0, 50] - now if we start a new incremental repair on [51, 100] we will (try to) stop the first one. Instead we should fail the new incremental repair request.
      • avoid stopping unrelated regular compactions - we should only stop regular compactions for the sstables the new anticompaction needs

      This requires us to keep track of which sstables are being compacted by a given compaction id.

        Attachments

          Activity

            People

            • Assignee:
              marcuse Marcus Eriksson
              Reporter:
              marcuse Marcus Eriksson
              Authors:
              Marcus Eriksson
              Reviewers:
              Blake Eggleston
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: