cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1099) make CFS.flushWriter_ size configurable
Date Tue, 01 Jun 2010 12:47:39 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873978#action_12873978
] 

Hudson commented on CASSANDRA-1099:
-----------------------------------

Integrated in Cassandra #452 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/452/])
    make CFS.flushWriter_ size configurable.  patch by Brandon Williams; reviewed by jbellis
for CASSANDRA-1099


> 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
>            Assignee: Brandon Williams
>            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.


Mime
View raw message