[CASSANDRA-4419] leveled compaction generates too small sstables

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 1.0.11
• Severity: Low
• Assignee: Sylvain Lebresne
• Reporter: Noa Resare

Authors

Sylvain Lebresne

Reviewers

Jonathan Ellis

• Created: 06/Jul/12 10:55
• Updated: 16/Apr/19 09:32
• Resolved: 12/Jul/12 17:52

Description

When I set sstable_size_in_mb to 96 I end up with sstable data files no larger than 60M.

This in turn messes up the LeveledManifest calculation since it finds compaction candidates by summing up the size of sstables at a particular level and comparing it to the configured size multiplied by the desired number of sstables at a level, resulting in ~20 sstables in level 1 instead of the 10 that one would expect from looking at LeveledManifest.

Some additional logging here reveals that the position parameter passed to LeveledCompactionTask.newSSTableSegmentThresholdReached() is significantly higher than the size of the output file.

Issue Links

• is related to: CASSANDRA-6698 Many too small SSTables when full repair