Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <33538011.1761274377877276.JavaMail.jira@thor>
Date: Thu, 20 May 2010 13:51:17 -0400 (EDT)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Updated: (CASSANDRA-1099) make CFS.flushWriter_ size
 configurable
In-Reply-To: <9618957.83611274109163152.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams updated CASSANDRA-1099:
----------------------------------------

    Attachment: 1099.txt

Patch adds a memtable_flush_writers config option.

> make CFS.flushWriter_ size configurable
> ---------------------------------------
>
>                 Key: CASSANDRA-1099
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1099
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: 1099.txt
>
>
> For small heaps (including our out-of-the-box 1G) we want to allow reducing this from the automatic (1 + 2 * DatabaseDescriptor.getAllDataFileLocations().length); having 3 memtables in the queue, plus another being written, is over 200MB which is a significant amount of data for the GC to chew through (see CASSANDRA-1014).
> For large heaps, we might also want to allow *increasing* this value, to accommodate load spikes better.
> Unfortunately making this configurable at runtime does not appear to be an option due to the lack of a setCapacity method on any of the BlockingQueue classes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.