cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Hermes (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-1007) Make memtable flush thresholds per-CF instead of global
Date Wed, 13 Oct 2010 21:36:34 GMT


Jon Hermes updated CASSANDRA-1007:

    Attachment: 1007.txt

M       conf/cassandra.yaml
Moves memtable settings into cf by demonstration.

M       src/java/org/apache/cassandra/db/
M       src/java/org/apache/cassandra/db/
M       src/java/org/apache/cassandra/db/
All the places where we previously asked for the global flushtime/size/ops now ask for it
on a per-CF basis.

M       src/java/org/apache/cassandra/config/
The bulk of the changes. This adds the new field, handles all its constructors, into and out
of avro/thrift, validation, and defaulting.

M       src/java/org/apache/cassandra/config/
M       src/java/org/apache/cassandra/config/
M       src/java/org/apache/cassandra/config/
M       src/java/org/apache/cassandra/config/
Changed the way we read in the YAML, and updated the converter to handle 0.6 -> 0.7 transitions.

M       src/java/org/apache/cassandra/thrift/
M       src/java/org/apache/cassandra/avro/
Updated add/update CF to add new fields and validate them appropriately.

M       interface/cassandra.genavro
M       interface/thrift/gen-java/org/apache/cassandra/thrift/
M       interface/thrift/gen-java/org/apache/cassandra/thrift/
M       interface/cassandra.thrift
Adds three new fields to the CfDef, and adds the generated bindings.

> 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