On Dec 14, 2010, at 21:07, Peter Schuller wrote:

> In that case, based on the strack trace, I wonder if you're hitting
> what I was hitting just yesterday/earlier today:
> 
>   https://issues.apache.org/jira/browse/CASSANDRA-1860
> 
> Which is suspected (currently being tested that it's gone with updated
> 0.7) to be due to:
> 
>   https://issues.apache.org/jira/browse/CASSANDRA-1847
> 
> If the corruption happens to be slightly different in your case, maybe
> it just ends up trying to allocate a large array instead of the
> failure mode I got (EOF or bad cfId) on the receiving end.
> 
> Can you try to reproduce with the latest 0.7 branch as of today?

I'll try to do so tomorrow.

> It seems very similar in nature at least based on the latest stack trace.

If it helps, I also found quite a few of these in the logs

org.apache.cassandra.db.UnserializableColumnFamilyException: Couldn't find 
cfId=224101

However a single cassandra instance locally (OSX, 1.6.0_22, mmap) runs just 
perfect for 
hours. No exceptions, no OOM. 

Reply via email to