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/05/28 22:35:45 UTC
[jira] Commented: (CASSANDRA-204) Replayed log data is not flushed
before logs are wiped
[ https://issues.apache.org/jira/browse/CASSANDRA-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714157#action_12714157 ]
Jonathan Ellis commented on CASSANDRA-204:
------------------------------------------
s/schedules on the executor/locks and checks for flush/
> 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.