cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1007) Make memtable flush thresholds per-CF instead of global
Date Thu, 14 Oct 2010 17:48:34 GMT


Brandon Williams commented on CASSANDRA-1007:

Tests fail to compile:

    [javac] Compiling 80 source files to /srv/cassandra/build/test/classes
    [javac] /srv/cassandra/test/unit/org/apache/cassandra/db/ cannot find
    [javac] symbol  : constructor CFMetaData(java.lang.String,java.lang.String,org.apache.cassandra.db.ColumnFamilyType,org.apache.cassandra.db.marshal.UTF8Type,<nulltype>,java.lang.String,int,boolean,double,int,int,org.apache.cassandra.db.marshal.BytesType,int,int,java.util.Map<byte[],org.apache.cassandra.config.ColumnDefinition>)
    [javac] location: class org.apache.cassandra.config.CFMetaData
    [javac]         return new CFMetaData(ks,
    [javac]                ^

> Make memtable flush thresholds per-CF instead of global
> -------------------------------------------------------
>                 Key: CASSANDRA-1007
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Assignee: Jon Hermes
>            Priority: Minor
>             Fix For: 0.7.0
>         Attachments: 1007.txt
> This is particularly useful in the scenario where you have a few CFs with a high volume
of overwrite operations; increasing the memtable size/op count means that you can do the overwrite
in memory before it ever hits disk.  Once on disk compaction is much more work for the system.
> But, you don't want to give _all_ your CFs that high of a threshold because the memory
is better used elsewhere, and because it makes commitlog replay unnecessarily painful.

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

View raw message