[CASSANDRA-14892] Possible corruption in compressed files with uncompressed chunks

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-alpha1, 4.0
• Component/s: Legacy/Local Write-Read Paths
• Bug Category: Correctness - Recoverable Corruption / Loss
• Severity: Normal
• Assignee: Branimir Lambov
• Reporter: Branimir Lambov

Authors

Branimir Lambov

Reviewers

Robert Stupp

• Created: 15/Nov/18 09:02
• Updated: 15/May/20 08:06
• Resolved: 29/Nov/18 14:29

Description

When deciding to switch to writing a chunk uncompressed in a compressed file (see CASSANDRA-10520) and that chunk is smaller than the full chunk size (only currently happens in the last chunk of the file), it may very rarely happen that the chunk is:

• bigger than the compression limit when compressed
• smaller than the compression limit when left uncompressed

If this happens the writer will write it uncompressed, but the reader will treat it as compressed and fail when attempting to read it.

Such chunks should be padded with 0s to the minimum uncompressed size.

Issue Links

• links to: branch
• links to: ci