You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Josh McKenzie (Jira)" <ji...@apache.org> on 2020/04/18 11:45:00 UTC
[jira] [Updated] (CASSANDRA-14892) Possible corruption in
compressed files with uncompressed chunks
[ https://issues.apache.org/jira/browse/CASSANDRA-14892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh McKenzie updated CASSANDRA-14892:
--------------------------------------
Bug Category: Parent values: Correctness(12982)Level 1 values: Recoverable Corruption / Loss(12986)
> Possible corruption in compressed files with uncompressed chunks
> ----------------------------------------------------------------
>
> Key: CASSANDRA-14892
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14892
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
> Reporter: Branimir Lambov
> Assignee: Branimir Lambov
> Priority: Normal
> Fix For: 4.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org