Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 35929 invoked from network); 26 Mar 2011 22:22:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 Mar 2011 22:22:16 -0000 Received: (qmail 59537 invoked by uid 500); 26 Mar 2011 22:22:15 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 59501 invoked by uid 500); 26 Mar 2011 22:22:15 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 59493 invoked by uid 99); 26 Mar 2011 22:22:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Mar 2011 22:22:15 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.213.172] (HELO mail-yx0-f172.google.com) (209.85.213.172) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Mar 2011 22:22:07 +0000 Received: by yxk30 with SMTP id 30so954115yxk.31 for ; Sat, 26 Mar 2011 15:21:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.53.3 with SMTP id b3mr2398920yba.11.1301178106215; Sat, 26 Mar 2011 15:21:46 -0700 (PDT) Sender: scode@scode.org Received: by 10.150.147.9 with HTTP; Sat, 26 Mar 2011 15:21:46 -0700 (PDT) X-Originating-IP: [90.233.79.15] In-Reply-To: References: Date: Sat, 26 Mar 2011 23:21:46 +0100 X-Google-Sender-Auth: 1eD7wLvIxNN6oy_pzYgKMjSVGR4 Message-ID: Subject: Re: ParNew (promotion failed) From: Peter Schuller To: user@cassandra.apache.org Cc: ruslan usifov Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org > So to resolve this i must tune young generation (HEAP_NEWSIZE) -Xmn, and > tune in_memory_compaction_limit_in_mb config parameter? More likely adjust the initial occupancy trigger and/or the heap size. Probably just the latter. This is assuming you're on 0.7 with mostly default JVM options. See cassandra-env.sh. In fact, you may even be helped by *decreasing* the young generation size if you're running a version which has a cassandra-env which specifies -Xmn. I'm not entirely sure because I don't know off hand exactly based on what the occupancy trigger is happening, but the young gen is large and the workload is such that young-gen gc:s promote a high percentage of it's data, I suspect that can lead to CMS triggering too late. (So this paragraph is speculation.) -- / Peter Schuller