cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Hermes (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CASSANDRA-1007) Make memtable flush thresholds per-CF instead of global
Date Wed, 13 Oct 2010 23:00:33 GMT

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

Jon Hermes edited comment on CASSANDRA-1007 at 10/13/10 6:58 PM:
-----------------------------------------------------------------

Nope, tests are now crashing and burning.

EDIT1:
test/conf/cassandra.yaml was still using global memtable settings, so that was the first error.
Now it's complaining that KSMetaData.deflate() isn't defined, which is broken.

      was (Author: jhermes):
    Nope, tests are now crashing and burning.
  
> Make memtable flush thresholds per-CF instead of global
> -------------------------------------------------------
>
>                 Key: CASSANDRA-1007
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1007
>             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.


Mime
View raw message