[
https://issues.apache.org/jira/browse/CASSANDRA-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019108#comment-13019108
]
Joaquin Casares commented on CASSANDRA-2430:
--------------------------------------------
And another sample error where this would help:
ERROR 23:21:03,693 Fatal exception in thread Thread[CompactionExecutor:1,1,main]
java.io.IOError: java.io.EOFException: attempted to skip 1647598019 bytes but
only skipped 27856771
at
org.apache.cassandra.io.sstable.SSTableIdentityIterator.<init>(SSTableIdentityIterator.java:117)
> 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
> Priority: Minor
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
