[CASSANDRA-17575] forceCompactionForTokenRange when using a wrapped range may include sstables not within that range

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.11.14, 4.0.6, 4.1-beta1, 4.1, 5.0-alpha1, 5.0
• Component/s: Local/Compaction
• Bug Category: Correctness - API / Semantic Implementation
• Severity: Normal
• Complexity: Normal
• Discovered By: Unit Test
• Platform: All
• Since Version: 3.10

Source Control Link

https://github.com/apache/cassandra/commit/4e410fc46da5d6759463230ab09a718178dbd4d9

Test and Documentation Plan

LeveledCompactionStrategyTest#testTokenRangeCompaction should be enough to cover this. The documentation of nodetool compact and StorageServiceMBean.forceKeyspaceCompactionForTokenRange should be updated.

• Assignee: Andres de la Peña
• Reporter: David Capwell

Authors

Andres de la Peña

Reviewers

Ekaterina Dimitrova

• Created: 22/Apr/22 20:50
• Updated: 12/Sep/23 13:02
• Resolved: 12/Aug/22 09:46

Description

This was found in CASSANDRA-17537

When you compact the range (32, 31] this should include everything BUT 32, but in the test org.apache.cassandra.db.compaction.LeveledCompactionStrategyTest#testTokenRangeCompaction it found that SSTables with the bounds (32, 32) were getting included in the set of SSTables to compact

Issue Links

• is caused by: CASSANDRA-10643 Implement compaction for a specific token range
• is related to: CASSANDRA-17537 nodetool compact should support using a key string to find the range to avoid operators having to manually do this
• links to: PR 3.11
• links to: PR 4.0
• links to: PR 4.1
• links to: PR trunk