It was not something you did wrong. The key cache format/classes involved
changed, there are a few jira issues around this:
https://issues.apache.org/jira/browse/CASSANDRA-4916
https://issues.apache.org/jira/browse/CASSANDRA-5253
Depending on how you moved between version you may or may not have
Yes, I know blowing them away would fix it and that is what I did, but I
want to understand why this happens in first place. I was upgrading from
1.1.10 to 1.2.3
On Fri, Apr 5, 2013 at 2:53 PM, Edward Capriolo wrote:
> This has happened before the save caches files were not compatible between
>
This has happened before the save caches files were not compatible between
0.6 and 0.7. I have ran into this a couple other times before. The good
news is the save key cache is just an optimization, you can blow it away
and it is not usually a big deal.
On Fri, Apr 5, 2013 at 2:55 PM, Arya Goud
Here is a chunk of bloom filter sstable skip messages from the node I
enabled DEBUG on:
DEBUG [OptionalTasks:1] 2013-04-04 02:44:01,450 SSTableReader.java (line
737) Bloom filter allows skipping sstable 39459
DEBUG [OptionalTasks:1] 2013-04-04 02:44:01,450 SSTableReader.java (line
737) Bloom filte
> skipping sstable due to bloom filter debug messages
What were these messages?
Do you have the logs from the start up ?
Cheers
-
Aaron Morton
Freelance Cassandra Consultant
New Zealand
@aaronmorton
http://www.thelastpickle.com
On 4/04/2013, at 6:11 AM, Arya Goudarzi wrote:
