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

Hudson commented on CASSANDRA-182:
----------------------------------

Integrated in Cassandra #151 (See 
[http://hudson.zones.apache.org/hudson/job/Cassandra/151/])
    Use arrayblockingqueue in commitlog executor; this cleans up the code a bit 
(performance is unaffected since the writes and syncs are far more expensive 
than any queue ops)
patch by jbellis; reviewed by Jun Rao for 
add config options for commitlog syncing
patch by jbellis; reviewed by Jun Rao for 
custom CommitLogExecutorService that can fsync per multiple CL additions
patch by jbellis; reviewed by Jun Rao for 
move log ops to callables on a threadpoolexecutor instead of synchronizing.  
this prepares the way to merge multiple add() calls into a single sync.
patch by jbellis; reviewed by Jun Rao for 
naive fsync-after-each-log-entry
patch by jbellis; reviewed by Jun Rao for 
mv AbstractWriter to its own top-level class and remove redundant IFileWriter
patch by jbellis; reviewed by Jun Rao for 
handle incomplete CL entries on recover
patch by jbellis; reviewed by Jun Rao for 


> CommitLog.add doesn't really force to disk
> ------------------------------------------
>
>                 Key: CASSANDRA-182
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-182
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.3
>            Reporter: Sandeep Tata
>            Assignee: Jonathan Ellis
>             Fix For: 0.4
>
>         Attachments: 
> 0001-CASSANDRA-182-handle-incomplete-CL-entries-on-recover.txt, 
> 0002-mv-AbstractWriter-to-its-own-top-level-class-and-remov.txt, 
> 0003-naive-fsync-after-each-log-entry.txt, 0004-threadpoolexecutor.txt, 
> 0005-custom-CommitLogExecutorService-that-can-fsync-per-mul.txt, 
> 0006-config-options.txt, 0007-arrayblockingqueue.txt, 0008-updates.txt, 
> CASSANDRA-182.patch
>
>
> CommitLog.add does't really force writes to disk. This could result in acked 
> writes being lost.

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

Reply via email to