Dealing with "Corrupt (negative) value length encountered"

2011-12-30 Thread Philippe
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 AbstractCassandraDaemo

Re: Dealing with "Corrupt (negative) value length encountered"

2012-01-02 Thread aaron morton
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.thelastpickl

Re: Dealing with "Corrupt (negative) value length encountered"

2012-01-03 Thread Philippe
I was able to scrub the node the repair that failed was running on. Are you saying the error could be displayed on that node but the bad data coming from another node ? Log inspection also showed many of these, they seem to happen around when a stream transfer finishes. ERROR [Thread-550876] 2012-

Re: Dealing with "Corrupt (negative) value length encountered"

2012-01-04 Thread aaron morton
> I was able to scrub the node the repair that failed was running on. Are you > saying the error could be displayed on that node but the bad data coming from > another node ? Yes. The error occurred the node was receiving a data stream from another, you will need to clean the source of the data.

Re: Dealing with "Corrupt (negative) value length encountered"

2012-01-05 Thread Philippe
Thanks Aaron, I was able to complete the repair by scrubbing the column family on all three replicas. Cheers 2012/1/4 aaron morton > I was able to scrub the node the repair that failed was running on. Are > you saying the error could be displayed on that node but the bad data > coming from anot