[
https://issues.apache.org/jira/browse/CASSANDRA-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-2006:
--------------------------------------
Attachment: 2006-v2.txt
v2 moves to trunk, adds a 25% fudge factor, and adds MeteredFlusherTest to
demonstrate handling 100 CFs in a workload that OOMs w/o this feature. (Note
that I disabled emergency GC-based flushing in the test config, so that doesn't
cause a false negative.)
> 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
> Fix For: 0.8
>
> Attachments: 2006-v2.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
