Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <848954454.1253504056132.JavaMail.jira@brutus>
Date: Sun, 20 Sep 2009 20:34:16 -0700 (PDT)
From: "Chris Goffinet (JIRA)" <jira@apache.org>
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


     [ https://issues.apache.org/jira/browse/CASSANDRA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Goffinet updated CASSANDRA-433:
-------------------------------------

    Attachment: 0001-CASSANDRA-433.-Consolidated-BMT-threshold-and-object.patch

Consolidated BMT threshold and object count sizes into getMemtableSize() and getMemtableObjectCount()

> 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, 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.