cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: Out of control memory consumption
Date Thu, 10 Feb 2011 18:36:42 GMT
Sounds like you need to use a larger heap or put less stuff in it
(memtables, caches).

On Thu, Feb 10, 2011 at 11:17 AM, Huy Le <huyle@springpartners.com> wrote:
> Yes, we had setting at 75 but JVM did not have enough time to do GC, so it
> abort GC'ing.   We lowered it to 50, but still had issue, so we lowered it
> again to 35.
>
> On Thu, Feb 10, 2011 at 12:11 PM, Oleg Anastasyev <oleganas@gmail.com>
> wrote:
>>
>> Huy Le <huyle <at> springpartners.com> writes:
>>
>> > Our CMS settings are:        -XX:CMSInitiatingOccupancyFraction=35
>> > \
>> -XX:+UseCMSInitiatingOccupancyOnly \
>> >
>>
>> Occupancy Fraction = 35 seems very low value. You instructed GC to make
>> collection as soon as memory usage is at 35% - i.e. about 1G. This seems
>> very
>> low for production.
>> Did you tried another setting for this parameter ? 75 seems safe one.
>>
>
>
>
> --
> Huy Le
> Spring Partners, Inc.
> http://springpadit.com
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Mime
View raw message