[
https://issues.apache.org/jira/browse/CASSANDRA-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276245#comment-13276245
]
Yuki Morishita commented on CASSANDRA-2430:
-------------------------------------------
CASSANDRA-2261 lets C* blacklist corrupted SSTables, so above errors shouldn't
happen from v1.1.1.
With DEBUG enabled, you can see which file get blacklisted. (see
https://github.com/apache/cassandra/blob/cassandra-1.1/src/java/org/apache/cassandra/io/sstable/SSTableReader.java#L810)
> Show list of possibly corrupt sstables when receiving errors
> ------------------------------------------------------------
>
> Key: CASSANDRA-2430
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2430
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.7.0
> Reporter: Joaquin Casares
> Assignee: Yuki Morishita
> Priority: Minor
> Fix For: 1.1.1
>
>
> On errors such as these:
> ERROR [CompactionExecutor:1] 2011-04-06 11:57:00,125
> AbstractCassandraDaemon.java (line 112) Fatal exception in thread
> Thread[CompactionExecutor:1,1,main]
> java.io.IOError:
> org.apache.cassandra.db.ColumnSerializer$CorruptColumnException: invalid
> column name length 0
> It would be nice to know which sstable, and perhaps sstables, are causing
> these errors. Any additional information would also be beneficial in helping
> narrow the scope of corruption.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
