e ./cassandra-0.7/bin/nodetool -h cassa7test01 cleanup
> Error occured while cleaning up keyspace keyspace
> java.util.concurrent.ExecutionException: java.io.IOException: Keys must be
> written in ascending order.
> at java.util.concurrent.FutureTask$S
On Wed, Jan 19, 2011 at 2:26 AM, aaron morton wrote:
> David,
> There was an issue similar to this reported during the 0.7 development
> https://issues.apache.org/jira/browse/CASSANDRA-1744 which was marked as
> duplicate with https://issues.apache.org/jira/browse/CASSANDRA-1743 It looks
a7test01 cleanup
> Error occured while cleaning up keyspace keyspace
> java.util.concurrent.ExecutionException: java.io.IOException: Keys must be
> written in ascending order.
>at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252)
>at java.util.concu
mething obvious?
$ time ./cassandra-0.7/bin/nodetool -h cassa7test01 cleanup
Error occured while cleaning up keyspace keyspace
java.util.concurrent.ExecutionException: java.io.IOException: Keys must be
written in ascending order.
at java.util.concurrent.FutureTask$Sync.innerGet(Futu
in thread Thread[HINTED-HANDOFF-POOL:1,5,main]java.util.concurrent.ExecutionException: javalang.RuntimeException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.io.IOException: Keys must be written in ascending order. at java.util.concurrent.FutureTask$Sync.innerGet(
I'm running the nightly trunk build from 2010-08-26_13-52-57 and got a bunch of java.io.IOException: Keys must be written in ascending order errors. Am running a 4 node cluster, this error occured on a single nodes. Eventually the node went OOM, not sure if it has anything to do with the
