On Fri, Jul 6, 2012 at 9:44 AM, rohit bhatia wrote:
> On Fri, Jul 6, 2012 at 4:47 AM, aaron morton wrote:
>> 12G Heap,
>> 1600Mb Young gen,
>>
>> Is a bit higher than the normal recommendation. 1600MB young gen can cause
>> some extra ParNew pauses.
> Thanks for heads up, i'll try tinkering on th
On Fri, Jul 6, 2012 at 4:47 AM, aaron morton wrote:
> 12G Heap,
> 1600Mb Young gen,
>
> Is a bit higher than the normal recommendation. 1600MB young gen can cause
> some extra ParNew pauses.
Thanks for heads up, i'll try tinkering on this
>
> 128 Concurrent writer
> threads
>
> Unless you are on
> 12G Heap,
> 1600Mb Young gen,
Is a bit higher than the normal recommendation. 1600MB young gen can cause some
extra ParNew pauses.
> 128 Concurrent writer
> threads
Unless you are on SSD this is too many.
> 1) Is using JDK 1.7 any way detrimental to cassandra?
as far as I know it's not full
Also,
Looking at gc log. I see messages like this across different servers
before they start dropping messages
"2012-07-04T10:48:20.336+: 96771.117: [GC 96771.118: [ParNew:
1367297K->57371K(1474560K), 0.0617350 secs]
6641571K->5340088K(12419072K), 0.0634460 secs] [Times: user=0.56
sys=0.01,
Our Cassandra cluster consists of 8 nodes(16 core, 32G ram, 12G Heap,
1600Mb Young gen, cassandra1.0.5, JDK 1.7, 128 Concurrent writer
threads). The replication factor is 2 with 10 column families and we
service Counter incrementing write intensive tasks(CL=ONE).
I am trying to figure out the bott
