I'm pretty sure that was a bug fixed in a later 0.6.x release so you might be
able to upgrade and the exceptions might go away. We run 0.6.13 with a minor
mod to support data expiration and will probably do so indefinitely since there
no way to upgrade without shutting our site down :(
-Anthon
> Is it possible to use nodetool repair to fix this with the current data set?
>
> I issued a repair command and the other nodes seem to be doing the
> correct things but I concerned by this: "Uncaught exception in thread
> Thread[ROW-READ-STAGE:4327,5,main]"
>
> Will the affect node ever be able
Hello,
In a cluster running 0.6.6 one node lost part of a data file due to an
operator error. An older file was moved in place to bring cassandra
up again.
Now we get lots of these in the log:
2011-08-27_10:30:55.26219 'ERROR [ROW-READ-STAGE:4327] 10:30:55,258
CassandraDaemon.java:87 Uncaught
