On Tue, 2011-03-01 at 18:27 +0000, Robert Collins wrote:
> This specific error is gone, and a new one is here. This may be data
> driven (I haven't deleted my cluster - in a rush this morning, will
> fiddle this arvo for you).
>
> INFO [CompactionExecutor:1] 2011-03-02 05:28:28,582
> CompactionManager.java (line 458) Compacted to
> /var/lib/cassandra/data/system/Schema-tmp-f-244-Data.db. 600,198 to
> 599,871 (~99% of original) bytes for 220 keys. Time: 225ms.
> ERROR [MigrationStage:1] 2011-03-02 05:28:28,589
> AbstractCassandraDaemon.java (line 114) Fatal exception in thread
> Thread[MigrationStage:1,5,main]
> org.apache.cassandra.config.ConfigurationException: Previous version
> mismatch. cannot apply.
> at org.apache.cassandra.db.migration.Migration.apply(Migration.java:115)
> at org.apache.cassandra.thrift.CassandraServer$2.call(CassandraServer.java:633)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:636)
> INFO [MigrationStage:1] 2011-03-02 05:28:28,595
> ColumnFamilyStore.java (line 665) switching in a fresh Memtable for
> OOPS at CommitLogContext(file='/var/lib/cassandra/commitlog/CommitLog-1299004019135.log',
> position=634361)
There was something wrong with 0.7.0 thru 0.7.3 .. I've uploaded 0.7.3
just now to the stable PPA. Once it is available, can you try installing
it and running
nodetool scrub
Which should fix on-disk problems created by those versions. The bug
report mentions IOExceptions, which I don't see above, but it
specifically references compaction as the root of this problem, so it
would appear related.
On Tue, 2011-03-01 at 18:27 +0000, Robert Collins wrote: utor:1] 2011-03-02 05:28:28,582 er.java (line 458) Compacted to cassandra/ data/system/ Schema- tmp-f-244- Data.db. 600,198 to raDaemon. java (line 114) Fatal exception in thread MigrationStage: 1,5,main] cassandra. config. ConfigurationEx ception: Previous version cassandra. db.migration. Migration. apply(Migration .java:115) cassandra. thrift. CassandraServer $2.call( CassandraServer .java:633) concurrent. FutureTask$ Sync.innerRun( FutureTask. java:334) concurrent. FutureTask. run(FutureTask. java:166) concurrent. ThreadPoolExecu tor.runWorker( ThreadPoolExecu tor.java: 1110) concurrent. ThreadPoolExecu tor$Worker. run(ThreadPoolE xecutor. java:603) Thread. run(Thread. java:636) re.java (line 665) switching in a fresh Memtable for t(file= '/var/lib/ cassandra/ commitlog/ CommitLog- 1299004019135. log',
> This specific error is gone, and a new one is here. This may be data
> driven (I haven't deleted my cluster - in a rush this morning, will
> fiddle this arvo for you).
>
> INFO [CompactionExec
> CompactionManag
> /var/lib/
> 599,871 (~99% of original) bytes for 220 keys. Time: 225ms.
> ERROR [MigrationStage:1] 2011-03-02 05:28:28,589
> AbstractCassand
> Thread[
> org.apache.
> mismatch. cannot apply.
> at org.apache.
> at org.apache.
> at java.util.
> at java.util.
> at java.util.
> at java.util.
> at java.lang.
> INFO [MigrationStage:1] 2011-03-02 05:28:28,595
> ColumnFamilySto
> OOPS at CommitLogContex
> position=634361)
There was something wrong with 0.7.0 thru 0.7.3 .. I've uploaded 0.7.3
just now to the stable PPA. Once it is available, can you try installing
it and running
nodetool scrub
Which should fix on-disk problems created by those versions. The bug
report mentions IOExceptions, which I don't see above, but it
specifically references compaction as the root of this problem, so it
would appear related.
https:/ /issues. apache. org/jira/ browse/ CASSANDRA- 2217