incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Coli <rc...@eventbrite.com>
Subject Re: Which SSTable caused CorruptSSTableException?
Date Tue, 25 Feb 2014 18:27:07 GMT
On Tue, Feb 25, 2014 at 9:48 AM, Ike Walker <ike.walker@flite.com> wrote:

> Running Cassandra 1.2.9 in AWS with a 12 host cluster, I am getting lots
> of CorruptSSTableException in system.log on one of my hosts.
>
> Is it possible to find out which SSTable(s) is/are corrupt?
>

This feature has been requested a few times. I suggest looking for a JIRA
and filing a feature request if one does not exist. If you do, please reply
and let the list know in order to close the circle for googlers. :)

In the interim, if you try to dump the files (to /dev/null?) via
sstable2jason (or sstablekeys in the case of a corrupt index file) you can
determine which file is corrupt. You can also attempt to correlate which
compaction thread is excepting with the files that it was trying to
compact, to narrow down the search.

=Rob

Mime
View raw message