[CASSANDRA-14870] The order of application of nodetool garbagecollect is broken

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.11.4, 4.0-alpha1, 4.0
• Component/s: Local/Compaction
• Severity: Normal
• Assignee: Branimir Lambov
• Reporter: Branimir Lambov

Authors

Branimir Lambov

Reviewers

Zhao Yang

• Created: 07/Nov/18 08:22
• Updated: 15/May/20 08:03
• Resolved: 13/Nov/18 11:10

Description

nodetool garbagecollect was intended to work from oldest sstable to newest, so that the collection in newer tables can purge tombstones over data that has been deleted.

However, SSTableReader.maxTimestampComparator currently sorts in the opposite order (the order changed in CASSANDRA-13776 and then back in CASSANDRA-14010), which makes the garbage collection unable to purge any tombstones.

Issue Links

• is related to: CASSANDRA-14099 LCS ordering of sstables by timestamp is inverted
• links to: 3.11 branch
• links to: 3.11 unit tests