incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ying Tang <ivytang0...@gmail.com>
Subject Re: 0.7.0beta3 Cassandra frequently log GC for ConcurrentMarkSweep
Date Mon, 06 Dec 2010 13:11:43 GMT
And after checking node who gc concurrentMarkSweep frequently ,it's OC(Current
old space capacity (KB)) is 1006016.0 ,it's OU(Old space utilization (KB).)
is also 1006016.0  ,almost all memory.
Dose this situation imply this heap size is set too low?

On Mon, Dec 6, 2010 at 8:07 PM, Ying Tang <ivytang0812@gmail.com> wrote:

> I hava a two node , running cassandra ,both's memory is 4G.
> First i set heap size to 2G ,both run normal .
> The i set heap size to 1G ,  the client who insert data to and read data
> from cassandra began throw Read\Write Unavailable Exception . And one
> cassandra node began  logging  GC for ConcurrentMarkSweep frequently  ,every
> ConcurrentMarkSweep 's time is over 5000ms.
> How this happen ? Why frequently ConcurrentMarkSweep GC ,not ParNew GC?
>
> --
> Best regards,
> Ivy Tang
>
>
>
>


-- 
Best regards,

Ivy Tang

Mime
View raw message