[ 
https://issues.apache.org/jira/browse/CASSANDRA-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684719#comment-13684719
 ] 

Jeremy Hanna commented on CASSANDRA-5646:
-----------------------------------------

It's generally recommended to run nodetool upgradesstables between any two 
major versions prior to doing any kind of streaming operation like move, 
bootstrap, or repair.  That will avoid any mixed version sstable issues.  I'm 
not sure what the guarantees are.  I believe each node can read the prior major 
version files, but sometimes the streaming operations have issues.
                
> Incompatible sstables hangs repair
> ----------------------------------
>
>                 Key: CASSANDRA-5646
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5646
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.5
>            Reporter: Radim Kolar
>
> repair session between 1.2.5 and 1.2.4:
> ERROR [Thread-11] 2013-06-16 13:39:39,359 CassandraDaemon.java (line 175) 
> Exception in thread Thread[Thread-11,5,main]
> java.lang.UnsupportedOperationException: SSTable C:\Program Files 
> (x86)\DataStax Community\data\data\test\sipdb\test-sipdb-hf-16-Data.db is not 
> compatible with current version ic
>       at 
> org.apache.cassandra.streaming.StreamIn.getContextMapping(StreamIn.java:77)
>       at 
> org.apache.cassandra.streaming.IncomingStreamReader.<init>(IncomingStreamReader.java:87)
>       at 
> org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.java:238)
>       at 
> org.apache.cassandra.net.IncomingTcpConnection.handleStream(IncomingTcpConnection.java:178)
>       at 
> org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:78)
> using nodetool netstats shows both sstables streaming at 0/XXXXXX. repair 
> never finished. After upgrading sstables to latest level (hf and ic should be 
> compatible) repair works fine.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to