cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-808) Need a way to skip corrupted data in SSTables
Date Tue, 12 Apr 2011 18:00:06 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-808.
--------------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 1.0)

nodetool scrub seems to address this adequately now.

> Need a way to skip corrupted data in SSTables
> ---------------------------------------------
>
>                 Key: CASSANDRA-808
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-808
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Stu Hood
>            Priority: Minor
>
> The new SSTable format will allow for checksumming of the data file, but as it stands,
we don't have a better way to handle the situation than throwing an Exception indicating that
the data is unreadable.
> We might want to add an option (triggerable via a command line flag?) to Cassandra that
will allow for skipping of corrupted keys/blocks in SSTables, to pretend they don't exist
rather than throwing the Exception.
> An administrator could temporarily enable the option and trigger a compaction to perform
a local repair of data, or they could leave it enabled constantly for hands-off recovery.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message