You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jackson Chung (JIRA)" <ji...@apache.org> on 2011/06/22 21:54:47 UTC
[jira] [Created] (CASSANDRA-2813) more info on logging when SSTable
cannot create the builder due to version mismatch
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
[jira] [Resolved] (CASSANDRA-2813) more info on logging when
SSTable cannot create the builder due to version mismatch
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-2813.
---------------------------------------
Resolution: Fixed
Fix Version/s: 0.8.2
Reviewer: jbellis
Assignee: Jackson Chung
committed, thanks!
> 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
> Assignee: Jackson Chung
> Priority: Minor
> Fix For: 0.8.2
>
> 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
[jira] [Commented] (CASSANDRA-2813) more info on logging when
SSTable cannot create the builder due to version mismatch
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053583#comment-13053583 ]
Hudson commented on CASSANDRA-2813:
-----------------------------------
Integrated in Cassandra-0.8 #185 (See [https://builds.apache.org/job/Cassandra-0.8/185/])
add path for sstable version failure message
patch by Jackson Chung; reviewed by jbellis for CASSANDRA-2813
jbellis : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1138692
Files :
* /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/io/sstable/SSTableWriter.java
> 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
> Assignee: Jackson Chung
> Priority: Minor
> Fix For: 0.8.2
>
> 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
[jira] [Updated] (CASSANDRA-2813) more info on logging when SSTable
cannot create the builder due to version mismatch
Posted by "Jackson Chung (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jackson Chung updated CASSANDRA-2813:
-------------------------------------
Attachment: 2813.patch
base on trunk
> 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