You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Eric Evans (JIRA)" <ji...@apache.org> on 2009/05/05 17:58:30 UTC
[jira] Commented: (CASSANDRA-76) Don't rely on flushkey_ special
value to force flush
[ https://issues.apache.org/jira/browse/CASSANDRA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706080#action_12706080 ]
Eric Evans commented on CASSANDRA-76:
-------------------------------------
01-eliminate-special-flush-key.txt (supercedes 0001-trigger-flushes-directly-without-use-of-flushKey.txt)
This changeset abstracts the logic for placing a flush on the queue into a new method, Memtable.enqueueFlush. enqueueFlush is called from both forceflush and put (when a threshold is exceeded), without the need to apply a special flushKey.
02-add-force-flush-to-mbean.txt
This patch adds ColumnFamilyStore.forceflush to the mbean so that it can be activate through the management agent.
> Don't rely on flushkey_ special value to force flush
> ----------------------------------------------------
>
> Key: CASSANDRA-76
> URL: https://issues.apache.org/jira/browse/CASSANDRA-76
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jonathan Ellis
> Assignee: Eric Evans
> Fix For: 0.4
>
> Attachments: 0001-trigger-flushes-directly-without-use-of-flushKey.txt, 01-eliminate-special-flush-key.txt, 02-add-force-flush-to-mbean.txt
>
>
> We can force flush programatically w/o needing this workaround.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.