Also, if you can, please be sure to try the new 0.7.3 release. We had a bug with the compaction of superColumns for instance that is fixed there (https://issues.apache.org/jira/browse/CASSANDRA-2104). It also ships with a new scrub command that tries to find if your sstables are corrupted and repair them in that event. I can be worth trying it too.--SylvainOn Fri, Mar 4, 2011 at 7:04 PM, Benjamin Coverston <email@example.com> wrote:
Can you attach the portion of your logs that shows the exceptions indicating corruption? Which version are you on right now?
On 3/4/11 10:42 AM, Terje Marthinussen wrote:We are seeing various other messages as well related to deserialization, so this seems to be some random corruption somewhere, but so far it may seem to be limited to supercolumns.
On Sat, Mar 5, 2011 at 2:26 AM, Terje Marthinussen <firstname.lastname@example.org> wrote:
Did you get anywhere on this problem?I am seeing similar errors unfortunately :(
I tried to add some quick error checking to the serialization, and it seems like the data is ok there.
Some indication that this occurs in compaction and maybe in hinted handoff, but no indication that it occurs for sstables with newly written data.
-- Ben Coverston DataStax -- The Apache Cassandra Company http://www.datastax.com/