cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nathan McCall <n...@vervewireless.com>
Subject Re: Problem with JVM? concurrent mode failure
Date Wed, 28 Apr 2010 16:40:28 GMT
 -XX:CMSInitiatingOccupancyFraction=75

It's at 90 by default on most systems. Turning this down to the above
would trigger the incremental collection to occur 75% full as opposed
to %90.

-Nate

On Wed, Apr 28, 2010 at 7:44 AM, Jonathan Ellis <jbellis@gmail.com> wrote:
> Yes, incremental mode is definitely contraindicated for Cassandra.
>
> On Wed, Apr 28, 2010 at 1:07 AM, Peter Schuller
> <peter.schuller@infidyne.com> wrote:
>>>         -XX:+CMSIncrementalMode \
>>>         -XX:+CMSIncrementalPacing \
>>
>> This may  not be an issue given your other VM opts, but just FYI I
>> have had some difficulty making the incremental CMS mode perform GC
>> work sufficiently aggressively to avoid concurrent mode failures
>> during significant garbage generation.
>>
>> You may want to give CMS a try in non-incremental mode (i.e., the
>> concurrent mark phase will be done in one burst, rather than spread
>> out over time, but still concurrently).
>>
>> --
>> / Peter Schuller
>>
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of Riptano, the source for professional Cassandra support
> http://riptano.com
>

Mime
View raw message