> I set the swappiness to 0 but the problem remained. The only way I've
> managed to avoid it is to use standard disk mode.
Ok. But so can I take it you have confirmed that the machine *is* in
fact swapping during these ParNew:s? I guess so since you mention it
helps to move to standard disk mode
Hi Pete,
I set the swappiness to 0 but the problem remained. The only way I've
managed to avoid it is to use standard disk mode.
On Sat, Jun 5, 2010 at 9:14 PM, Peter Schuller
wrote:
>> INFO 17:54:18,567 GC for ParNew: 1522 ms, 69437384 reclaimed leaving
>> 979692384
>> used; max is 442466304
As promised on IIRC we also have collected some information as we are
seeing (probably) the same problem.
https://issues.apache.org/jira/browse/CASSANDRA-1177
On Wed, Jun 9, 2010 at 14:11, aaron morton wrote:
> May be related to CASSANDRA-1014
> https://issues.apache.org/jira/browse/CASSANDRA-10
May be related to CASSANDRA-1014
https://issues.apache.org/jira/browse/CASSANDRA-1014
And this discussion
http://www.mail-archive.com/user@cassandra.apache.org/msg02923.html
Aaron
On 6 Jun 2010, at 08:14, Peter Schuller wrote:
>> INFO 17:54:18,567 GC for ParNew: 1522 ms, 69437384 reclaimed lea
> INFO 17:54:18,567 GC for ParNew: 1522 ms, 69437384 reclaimed leaving
> 979692384
> used; max is 4424663040
> INFO 17:54:22,567 GC for ParNew: 1989 ms, 69323576 reclaimed leaving
> 981439840
> used; max is 4424663040
> INFO 17:54:26,187 GC for ParNew: 1337 ms, 69447160 reclaimed leaving
> 98
I'm seeing lots of ParNew messages which is affected performance,
along the lines of:
INFO 17:54:18,567 GC for ParNew: 1522 ms, 69437384 reclaimed leaving 979692384
used; max is 4424663040
INFO 17:54:22,567 GC for ParNew: 1989 ms, 69323576 reclaimed leaving 981439840
used; max is 4424663040
INF
