cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-2216) Compaction can echo data which breaks upon sstable format changes
Date Tue, 22 Feb 2011 12:26:38 GMT


Sylvain Lebresne updated CASSANDRA-2216:

    Attachment: 0001-Don-t-echo-data-during-compaction.patch

Attached patch completely remove the echoing of data when we have only one row. We could easily,
as in CASSANDRA-2211, echo data if the sstable we are echoing from is at the last version.

However, not doing so will allow potentially corrupted sstable to get repaired by compaction
(in the case of corruption from the bloom filter change).

We could add back the echoing optimisation later on.

> Compaction can echo data which breaks upon sstable format changes
> -----------------------------------------------------------------
>                 Key: CASSANDRA-2216
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Critical
>              Labels: compaction
>             Fix For: 0.7.3
>         Attachments: 0001-Don-t-echo-data-during-compaction.patch
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> While compaction, if for a row we have only 1 sstable holding data, we echo this data.
This breaks when we change the data format, creating mixed (corrupted) sstable.
> (I suspect this is the cause of CASSANDRA-2195, but opening a new ticket until we can
confirm that hunch)

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message