On Tue, Aug 3, 2010 at 10:47 AM, Maciej Lisowski <m.lisow...@powerprice.pl> wrote: > Hi all, > > I’m new here and new with Cassandra and I’ve got problem to run it (v. > 0.6.4) with jdk1.6.0_21. > > When I type “cassandra” to run it I get error: > > > > ERROR 16:23:53,803 Uncaught exception in thread > Thread[ROW-MUTATION-STAGE:5,5,main] > > java.util.concurrent.ExecutionException: java.lang.RuntimeException: > java.lang.NullPointerException > > at > java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) > > at java.util.concurrent.FutureTask.get(FutureTask.java:83) > > at > org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor.afterExecute(DebuggableThreadPoolExecutor.java:86) > > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:888) > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > > at java.lang.Thread.run(Thread.java:619) > > Caused by: java.lang.RuntimeException: java.lang.NullPointerException > > at > org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:34) > > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > > at > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > > ... 2 more > > Caused by: java.lang.NullPointerException > > at > org.apache.cassandra.db.Table$TableMetadata.getColumnFamilyId(Table.java:131) > > at org.apache.cassandra.db.Table.getColumnFamilyId(Table.java:364) > > at > org.apache.cassandra.db.commitlog.CommitLog$4.runMayThrow(CommitLog.java:256) > > at > org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30) > > ... 6 more > > > > I was looking for info what could happen but I didn’t find… can someone help > me with this? > > If I have to send something more (configuration or whatever) let me know > > > > Maciek
Something similar happened to me when upgrading from 6.1 -> 6.2. Even though the on-disk format of the SSTABLES is the same, sometimes the wire-format serialization of Future Tasks change. If that is the case, it means that the upgrade can NOT be done with a rolling restart. I am not sure this is the case here but that might help. Edward
