at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:9
08)
at java.lang.Thread.run(Thread.java:662)
Dan
-Original Message-
From: Jonathan Ellis [mailto:jbel...@gmail.com]
Sent: December-04-10 22:45
To: user
Subject: Re: Various exceptions on 0.7
At least one of your
At least one of your nodes is sending garbage to the others.
Either there's a bug in the bleeding edge code you are running (did
you try rc1?) or you do have nodes on different versions or you have a
hardware problem.
On Sat, Dec 4, 2010 at 5:51 PM, Dan Hendry wrote:
> Here are two other errors
Here are two other errors which appear frequently:
ERROR [MutationStage:29] 2010-12-04 17:47:46,931 RowMutationVerbHandler.java
(line 83) Error in row mutation
java.io.IOException: Invalid localDeleteTime read: 0
at
org.apache.cassandra.db.SuperColumnSerializer.deserialize(SuperColumn.java
No, all nodes are running very recent (< 2 day old) code out of the 0.7
branch. This cluster has always had 0.7 RC1(+) code running on it
On Sat, Dec 4, 2010 at 6:24 PM, Jonathan Ellis wrote:
> Are you mixing different Cassandra versions?
>
> On Sat, Dec 4, 2010 at 4:58 PM, Dan Hendry
> wrote:
Are you mixing different Cassandra versions?
On Sat, Dec 4, 2010 at 4:58 PM, Dan Hendry wrote:
> To be clear, I had to interrupt a clean operation earlier in the day be
> killing the cassandra process. Now the node works for awhile,
> but continually logging the "Error in row mutation" errors the
To be clear, I had to interrupt a clean operation earlier in the day be
killing the cassandra process. Now the node works for awhile,
but continually logging the "Error in row mutation" errors then eventually
logs a "Fatal exception in thread" error. After which, the process stays
alive but there s
