Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 7 Apr 2011 06:29:05 +0000 (UTC)
From: "Stu Hood (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <563139000.39985.1302157745870.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <712164.55091295426088991.JavaMail.jira@thor>
Subject: [jira] [Commented] (CASSANDRA-2006) Serverwide caps on memtable
 thresholds
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Stu Hood commented on CASSANDRA-2006:
-------------------------------------

+1
I'm very excited about this change: my last nitpick is that the flush_largest_memtables_at and memtable_total_space_in_mb settings could be made more consistent. At the absolute minimum, they should refer to one another in the config file, but I'm wondering how we might unify the 3 or 4 different reasons for flushing in our monitoring/logging somehow.

Also, we should start making a plan to deprecate the per-cf settings, or convert them into fractions as mentioned above.

> Serverwide caps on memtable thresholds
> --------------------------------------
>
>                 Key: CASSANDRA-2006
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2006
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Stu Hood
>            Assignee: Jonathan Ellis
>             Fix For: 0.8
>
>         Attachments: 2006-v2.txt, 2006-v3.txt, 2006.txt, jamm-0.2.jar
>
>
> By storing global operation and throughput thresholds, we could eliminate the "many small memtables" problem caused by having many CFs. The global threshold would be set in the config file, to allow different classes of servers to have different values configured.
> Operations occurring in the memtable would add to the global counters, in addition to the memtable-local counters. When a global threshold was violated, the memtable in the system that was using the largest fraction of it's local threshold would be flushed. Local thresholds would continue to act as they always have.
> The result would be larger sstables, safer operation with multiple CFs and per node tuning.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira