Return-Path: Delivered-To: apmail-incubator-cassandra-commits-archive@minotaur.apache.org Received: (qmail 99964 invoked from network); 23 Sep 2009 18:33:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Sep 2009 18:33:40 -0000 Received: (qmail 90804 invoked by uid 500); 23 Sep 2009 18:33:40 -0000 Delivered-To: apmail-incubator-cassandra-commits-archive@incubator.apache.org Received: (qmail 90777 invoked by uid 500); 23 Sep 2009 18:33:40 -0000 Mailing-List: contact cassandra-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-dev@incubator.apache.org Delivered-To: mailing list cassandra-commits@incubator.apache.org Received: (qmail 90767 invoked by uid 99); 23 Sep 2009 18:33:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Sep 2009 18:33:39 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Sep 2009 18:33:37 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 066DC234C004 for ; Wed, 23 Sep 2009 11:33:16 -0700 (PDT) Message-ID: <1834436629.1253730796011.JavaMail.jira@brutus> Date: Wed, 23 Sep 2009 11:33:16 -0700 (PDT) From: "Jonathan Ellis (JIRA)" To: cassandra-commits@incubator.apache.org Subject: [jira] Updated: (CASSANDRA-433) Remove item flush limit in BinaryMemtable In-Reply-To: <364973826.1252432677894.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CASSANDRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-433: ------------------------------------- Attachment: 433.patch from irc: jbellis: if you really use different sizes for BMt and normal Mt then i think we should have different settings. i'm just not sure why you'd want to do that goffinet: we wouldnt want it to run that high [a heap] at all times; we'd rather use the ram for FS cache jbellis: so if you do want different sizes for Mt/BMt let's just leave the separate BMt setting in and not make ops have to mess with things when bulk load is done goffinet: ok here is patch. > Remove item flush limit in BinaryMemtable > ----------------------------------------- > > Key: CASSANDRA-433 > URL: https://issues.apache.org/jira/browse/CASSANDRA-433 > Project: Cassandra > Issue Type: Improvement > Components: Core > Affects Versions: 0.5 > Reporter: Johan Oskarsson > Assignee: Chris Goffinet > Fix For: 0.5 > > Attachments: 0001-CASSANDRA-433.-Consolidated-BMT-threshold-and-object.patch, 433.patch, CASSANDRA-433.patch > > > The BinaryMemtable flushes in memory data to disk when the size of the data reaches a certain limit. There is also a hard coded limit that initiates the flush when more then 50000 items have been inserted. That causes issues if a lot of small items are inserted, we should remove or make the limit configurable. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.