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-2430) Show list of possibly corrupt sstables when receiving errors
Date Tue, 15 May 2012 21:39:10 GMT

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

Jonathan Ellis resolved CASSANDRA-2430.
---------------------------------------

       Resolution: Not A Problem
    Fix Version/s:     (was: 1.1.1)
         Assignee:     (was: Yuki Morishita)

Thanks, Yuki.
                
> 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.
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

        

Mime
View raw message