cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-445) commitlog may consider writes flushed, that are not yet
Date Fri, 18 Sep 2009 13:05:16 GMT

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

Hudson commented on CASSANDRA-445:
----------------------------------

Integrated in Cassandra #201 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/201/])
    commitlog may consider writes flushed, that are not yet; patched by junrao; reviewed by
jbellis for 


> commitlog may consider writes flushed, that are not yet
> -------------------------------------------------------
>
>                 Key: CASSANDRA-445
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-445
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jun Rao
>            Priority: Critical
>             Fix For: 0.5
>
>         Attachments: issue445.patchv1, issue445.patchv2
>
>
> Jun Rao explains:
> Suppose there are 3 updates u1, u2, and u3. They are written to commit log in that order.
If u1 and u3 are applied to memtable first and at that point, a flush is triggered. After
the flush completes, it will move the commit log restarting position based on the log for
u3. However, u2 hasn't been persisted on disk yet. This means that if the node dies now, the
recovery logic won't replay u2 from the log.

-- 
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