cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Coverston (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1717) Cassandra cannot detect corrupt-but-readable column data
Date Wed, 02 Mar 2011 21:11:37 GMT


Benjamin Coverston commented on CASSANDRA-1717:

Would we really save that much by waiting until #16 is done? Perhaps we should take a shot
at this in 0.7. Right now it's possible to have data corrupted, then replicated leading to
loss of data.

> Cassandra cannot detect corrupt-but-readable column data
> --------------------------------------------------------
>                 Key: CASSANDRA-1717
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>             Fix For: 0.8
>         Attachments: checksums.txt
> Most corruptions of on-disk data due to bitrot render the column (or row) unreadable,
so the data can be replaced by read repair or anti-entropy.  But if the corruption keeps column
data readable we do not detect it, and if it corrupts to a higher timestamp value can even
resist being overwritten by newer values.

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


View raw message