If it's GCing frequently and each CMS is only collecting a small
fraction of the old gen, then your heap is probably too small.
(GCInspector only logs collections that take over 1s, which should
never include ParNew.)
On Mon, Dec 6, 2010 at 7:11 AM, Ying Tang wrote:
> And after checking node who
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 wrot
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 ConcurrentM
