A few month ago, we've got a similar issue on 1.2.6 :
https://issues.apache.org/jira/browse/CASSANDRA-5706

But it has been fixed and did not encountered this issue anymore (we're also on 1.2.10)


2013/11/14 olek.stasiak@gmail.com <olek.stasiak@gmail.com>
Yes, as I wrote in first e-mail.  When I removed key cache file
cassandra started without further problems.
regards
Olek

2013/11/13 Robert Coli <rcoli@eventbrite.com>:
>
> On Wed, Nov 13, 2013 at 12:35 AM, Tom van den Berge <tom@drillster.com>
> wrote:
>>
>> I'm having the same problem, after upgrading from 1.2.3 to 1.2.10.
>>
>> I can remember this was a bug that was solved in the 1.0 or 1.1 version
>> some time ago, but apparently it got back.
>> A workaround is to delete the contents of the saved_caches directory
>> before starting up.
>
>
> Yours is not the first report of this I've heard resulting from a 1.2.x to
> 1.2.x upgrade. Reports are of the form "I had to nuke my saved_caches or <I
> couldn't start my node, it OOMED, etc.>".
>
> https://issues.apache.org/jira/browse/CASSANDRA-6325
>
> Exists, but doesn't seem  to be the same issue.
>
> https://issues.apache.org/jira/browse/CASSANDRA-5986
>
> Similar, doesn't seem to be an issue triggered by upgrade..
>
> If I were one of the posters on this thread, I would strongly consider
> filing a JIRA on point.
>
> @OP (olek) : did removing the saved_caches also fix your problem?
>
> =Rob
>
>



--
Fabien Rousseau


www.yakaz.com