This happens when you flush and there was no data in the binarymemtable. It's harmless (everything that does have data, still gets flushed).
Since you're running from svn you can update to the latest 0.4 code though which fixes the exception. On Wed, Nov 18, 2009 at 1:43 PM, kevin <[email protected]> wrote: > i get this error on cassandra when i do nodeprobe flush. > nodeprobe -host x.x.x.x flush > > > > 11:36:53,008 ERROR DebuggableThreadPoolExecutor:120 - Error in executor > futuretask > java.util.concurrent.ExecutionException: java.lang.AssertionError > 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:112) > 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.AssertionError > at > org.apache.cassandra.db.BinaryMemtable.getSortedKeys(BinaryMemtable.java:127) > at > org.apache.cassandra.db.ColumnFamilyStore$2.run(ColumnFamilyStore.java:947) > 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 > > > > am running svn version, > > Revision: 831540 > Node Kind: directory > Schedule: normal > Last Changed Author: jbellis > Last Changed Rev: 831433 > Last Changed Date: 2009-10-30 12:45:38 -0700 (Fri, 30 Oct 2009) >
