cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jackson Chung (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-2813) more info on logging when SSTable cannot create the builder due to version mismatch
Date Wed, 22 Jun 2011 19:54:47 GMT
more info on logging when SSTable cannot create the builder due to version mismatch
-----------------------------------------------------------------------------------

                 Key: CASSANDRA-2813
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2813
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Jackson Chung
            Priority: Minor
         Attachments: 2813.patch

When run into the following:

2011-06-21 22:44:43,308 INFO [org.apache.cassandra.streaming.StreamOutSession] - Streaming
to /10.128.64.163
2011-06-21 22:44:51,993 ERROR [org.apache.cassandra.service.AbstractCassandraDaemon] - Fatal
exception in thread Thread[Thread-17651,5,main]
java.lang.RuntimeException: Cannot recover SSTable with version a (current version f).
at org.apache.cassandra.io.sstable.SSTableWriter.createBuilder(SSTableWriter.java:237)
at org.apache.cassandra.db.CompactionManager.submitSSTableBuild(CompactionManager.java:938)
at org.apache.cassandra.streaming.StreamInSession.finished(StreamInSession.java:107)
at org.apache.cassandra.streaming.IncomingStreamReader.readFile(IncomingStreamReader.java:112)
at org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReader.java:61)
at org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)

There is no indication on which SSTable is at fault. To recover from this, one would need
to run nodetool scrub.

This may however take some time, depending the SSTables' sizes, and it is possible that only
1 keyspace or CF is needed to be rebuilt by scrub.

It'd be nice to print more details of the SSTable here in case the end-user prefers to just
scrub the keyspace/cf in question.


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

        

Mime
View raw message