Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 30544 invoked from network); 12 Apr 2011 21:07:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Apr 2011 21:07:40 -0000 Received: (qmail 55515 invoked by uid 500); 12 Apr 2011 21:07:38 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 55477 invoked by uid 500); 12 Apr 2011 21:07:38 -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 55444 invoked by uid 500); 12 Apr 2011 21:07:38 -0000 Delivered-To: apmail-incubator-cassandra-user@incubator.apache.org Received: (qmail 55429 invoked by uid 99); 12 Apr 2011 21:07:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Apr 2011 21:07:38 +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.210.175] (HELO mail-iy0-f175.google.com) (209.85.210.175) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Apr 2011 21:07:29 +0000 Received: by iye7 with SMTP id 7so7583338iye.6 for ; Tue, 12 Apr 2011 14:07:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.43.59.132 with SMTP id wo4mr9796394icb.406.1302642428424; Tue, 12 Apr 2011 14:07:08 -0700 (PDT) Sender: scode@scode.org Received: by 10.231.208.65 with HTTP; Tue, 12 Apr 2011 14:07:08 -0700 (PDT) X-Originating-IP: [213.114.145.159] In-Reply-To: <1302641755259-6266726.post@n2.nabble.com> References: <1302633374663-6266221.post@n2.nabble.com> <1302641755259-6266726.post@n2.nabble.com> Date: Tue, 12 Apr 2011 23:07:08 +0200 X-Google-Sender-Auth: J7eNJR_R6C7vtOxBPZ5GhO0M0x8 Message-ID: Subject: Re: flush_largest_memtables_at messages in 7.4 From: Peter Schuller To: user@cassandra.apache.org Cc: cassandra-user@incubator.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org > Yes Without checking I don't know the details of the memtable threshold calculations enough to be sure whether large columns are somehow causing the size estimations to be ineffective (off hand I would expect the reverse since the overhead of the Java object structures become much less significant); but if this is not the case, then this particular problem should be a matter of adjusting heap size according to your memtable thresholds. I.e., increase heap size and/or decrease memtable flush thresholds. -- / Peter Schuller