cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <>
Subject upgrading to 1.0.3+
Date Wed, 07 Dec 2011 23:35:56 GMT
I noticed this when upgrading a cluster from 1.0.1 to 1.0.5. 

We moved one node up to 1.0.5 to test everything was ok and a repair ran from that node. It
streamed files with the new minor file version number to nodes that were 1.0.1 

On restarting one of the nodes while still at 1.0.1 we got this…

 INFO [SSTableBatchOpen:1] 2011-12-07 21:56:19,885 (line 133) Opening /home/cassandra/data/spi/hits_sort-h-15
(112704 bytes)
ERROR [main] 2011-12-07 21:56:19,900 (line 354) Exception encountered
during startup
java.lang.RuntimeException: Can't open sstables from the future! Current version h, found
file: /home/cassandra/data/spi/email_mailers-hb-101
        at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(
        at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(
        at org.apache.cassandra.db.Table.initCf(
        at org.apache.cassandra.db.Table.<init>(
        at org.apache.cassandra.service.AbstractCassandraDaemon.setup(
        at org.apache.cassandra.service.AbstractCassandraDaemon.activate(
        at org.apache.cassandra.thrift.CassandraDaemon.main(

I think because the 1.0.1 node did not have this see

Perhaps something should be added to NEWS.txt to say all nodes should be on 1.0.3 before running
a repair?


p.s. Hello everyone :)

Aaron Morton
Freelance Developer

Aaron Morton
Freelance Developer

View raw message