cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-204) Replayed log data is not flushed before logs are wiped
Date Wed, 22 Jul 2009 22:19:15 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-204:
-------------------------------------

    Fix Version/s:     (was: 0.4)
                   0.3

> Replayed log data is not flushed before logs are wiped
> ------------------------------------------------------
>
>                 Key: CASSANDRA-204
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-204
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Critical
>             Fix For: 0.3
>
>         Attachments: 204.patch
>
>
> The memtable created by replaying commit logs on startup is supposed to be flushed as
a SSTable before the commitlog is removed, but this is not happening.  So you can lose data
by doing the following:
> 1. insert data
> 2. restart cassandra (using kill, to force replay)
> 3. restart cassandra again

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