More information ... My cluster is in the state where I can read, but not write, again. I used CLI to drop and recreate my keyspace and CFs. I then started inserting my data. Before inserting all my test data I starting getting TimedOutException on the client (Hector), then I realized it was in the state where writes are no longer working. During all my writes I am reading as well.
Nodetool reports all nodes are "up", thrift is running, gossip is active, and all are 1.0.0-beta1 On 9/23/11 9:40 AM, "Todd Burruss" <bburr...@expedia.com> wrote: >Fyi Š I am seeing the exception (at end of message) using 1.0-beta1. > >Notes: > >- I was running 0.8.5 before dropping in 1.0-beta1 >- upgraded yaml file to be 1.0 >- some CFs were created in 0.8.5 and some in 1.0-beta1 > >A couple of observations after seeing this: > >- cannot nicely kill cassandra, must use kill -9 >- the CLI can connect and 'get' at ONE or QUORUM, but cannot 'set' at >either CL > > >INFO [HintedHandoff:4] 2011-09-22 22:59:27,626 HintedHandOffManager.java >(line 259) Started hinted handoff for token: >150124573641590498586782915043427152112 with IP: /10.185.35.39 >ERROR [HintedHandoff:4] 2011-09-22 22:59:27,648 >AbstractCassandraDaemon.java (line 133) Fatal exception in thread >Thread[HintedHandoff:4,5,main] >java.lang.AssertionError > at >org.apache.cassandra.db.HintedHandOffManager.deliverHintsToEndpoint(Hinted >HandOffManager.java:282) > at >org.apache.cassandra.db.HintedHandOffManager.access$100(HintedHandOffManag >er.java:81) > at >org.apache.cassandra.db.HintedHandOffManager$2.runMayThrow(HintedHandOffMa >nager.java:333) > at >org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30) > at >java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor. >java:886) > at >java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java >:908) > at java.lang.Thread.run(Thread.java:662) >
