cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <aa...@thelastpickle.com>
Subject Re: Dealing with "Corrupt (negative) value length encountered"
Date Mon, 02 Jan 2012 10:26:47 GMT
I would try to nodetool scrub the data on the node that that sent the bad data in the stream.
You may be able to work which node from the logs, or it may be easier to just scrub them all.


Hope that helps. 
 
-----------------
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com

On 31/12/2011, at 12:20 AM, Philippe wrote:

> Hello,
> Running a combination of 0.8.6 and 0.8.8 with RF=3, I am getting the following while
repairing one node (all other nodes completed successfully).
> Can I just stop the instance, erase the SSTable and restart cleanup ?
> Thanks
> 
> ERROR [Thread-402484] 2011-12-29 14:51:03,687 AbstractCassandraDaemon.java (line 139)
Fatal exception in thread Thread[Thread-402484,5,main]
> java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.io.IOError:
java.io.IOException: Corrupt (negative) value length encountered
>         at org.apache.cassandra.streaming.StreamInSession.closeIfFinished(StreamInSession.java:154)
>         at org.apache.cassandra.streaming.IncomingStreamReader.read(IncomingStreamReader.java:63)
>         at org.apache.cassandra.net.IncomingTcpConnection.stream(IncomingTcpConnection.java:189)
>         at org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:117)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOError: java.io.IOException:
Corrupt (negative) value length encountered
>         at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
>         at java.util.concurrent.FutureTask.get(FutureTask.java:83)
>         at org.apache.cassandra.streaming.StreamInSession.closeIfFinished(StreamInSession.java:138)
>         ... 3 more
> 


Mime
View raw message