First check your node for IO errors. You have some bad data there.
When you restart cassandra it may identify which sstables are corrupt. You can
then stop the node and remove them.
You will then need to run repair to replace the missing data.
Hope that helps.
-
Aaron Morto
I may have found a trigger that is causing these problems. Anyone seen
these compaction problems in 1.1? I did run scrub on all my 1.0 data to
convert it to 1.1 and fix level-manifest problems before I started running
1.1.
1 node:
ERROR [CompactionExecutor:281] 2013-02-06 23:56:16,183
AbstractCass
I've gotten timeouts on clients when using Cassandra 1.1.8 in a cluster of
12 nodes, but I don't see the same behavior when using Cassandra 1.0.10.
So, to do a controlled experiment, the following was tried:
1. Started with Cassandra 1.0.10. Built a database and ran our test tools
against it to bu
