cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-134) Support flush based on timer interval, in addtion to size
Date Tue, 05 May 2009 21:39:36 GMT


Jonathan Ellis updated CASSANDRA-134:

    Attachment: 134-v2.patch

make forced flush a no-op when there is nothing to flush.  this allows cleaning up flush logic
a bit too.  (if there is nothing being flushed then ipso facto there will not be any clog
segments we can reclaim.)

> Support flush based on timer interval, in addtion to size
> ---------------------------------------------------------
>                 Key: CASSANDRA-134
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jun Rao
>            Assignee: Jun Rao
>         Attachments: 134-v2.patch, issue134.patchv1, issue134.patchv2
> Today, the CFs are flushed purely based on the size of the data accumulated in Memtable.
If a table has multiple CFs and some CFs are updated at a much slower pace than others, this
can prevent a larger number of log files from being deleted. This is because the CF bit in
the log header is only turned off when a CF is flushed. A log can't be deleted until all CF
bits in the header are cleared. One solution is to add a background flusher that periodically
force-flushes every CF.

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

View raw message