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.stas...@gmail.com
> Yes, as I wrote in first e-mail. When I removed key cache file
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 :
>
> On Wed, Nov 13, 2013 at 12:35 AM, Tom van den Berge
> wrote:
>>
>> I'm having the same problem, after upgrading from 1.2.3 to 1.2.10.
>>
>> I can r
On Wed, Nov 13, 2013 at 12:35 AM, Tom van den Berge 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 s
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.
Tom
On Tue, Nov 12, 201
> -6 machines which 8gb RAM each and three 150GB disks each
> -default heap configuration
With 8GB the default heap is 2GB, try kicking that up to 4GB and a 600 to 800
MB new heap.
I would guess for the data load you have 2GB is not enough.
hope that helps.
-
Aaron Morton
Ne
Hello,
I'm facing OOM on reading key_cache
Cluster conf is as follows:
-6 machines which 8gb RAM each and three 150GB disks each
-default heap configuration
-deafult key cache configuration
-the biggest keyspace has abt 500GB size (RF: 2, so in fact there is
250GB of raw data).
After upgrading fir
