You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2009/08/15 03:42:14 UTC
[jira] Commented: (CASSANDRA-367) CommitLog does not flush on
writes
[ https://issues.apache.org/jira/browse/CASSANDRA-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743518#action_12743518 ]
Jonathan Ellis commented on CASSANDRA-367:
------------------------------------------
I'd rather not call flush every add if possible. What problems are you seeing?
(To be pedantic: the change in the revision in question moved from using an unbuffered writer, to using a buffered one. Not removing a pre-existing flush.)
> CommitLog does not flush on writes
> ----------------------------------
>
> Key: CASSANDRA-367
> URL: https://issues.apache.org/jira/browse/CASSANDRA-367
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.4
> Reporter: Chris Goffinet
> Assignee: Jonathan Ellis
> Priority: Blocker
> Fix For: 0.4
>
> Attachments: 0001-CASSANDRA-367-Added-flush.patch
>
>
> When you write data to CommitLog, we are not calling a flush() in class LogRecordAdder.
> Is this acceptable? We added flush() and its working now. This bug was introduced when things were consolidated in r799942
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.