cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ivo Meißner (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4481) Commitlog not replayed after restart - data lost
Date Fri, 03 Aug 2012 10:33:03 GMT

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

Ivo Meißner commented on CASSANDRA-4481:
----------------------------------------

I am still trying to narrow it down. I have created a new keyspace ("testkeyspace") with the
same configuration and structure. 
When I only use the testkeyspace, the error does not occur, everything in the commitlog is
available after reboot: 

The following works as expected: 
1. Insert dataA in testkeyspace
2. Reboot -> 1 replayed mutations
3. Get dataA returns data as expected

The following does not work:
1. Insert dataA in testkeyspace
2. Get dataA from testkeyspace -> returns data as expected
3. Insert dataB in brokenkeyspace
4. Get dataB from brokenkeypsace -> returns data as expected
5. Reboot -> 0 replayed mutations
6. Get dataA from testkeyspace -> NO DATA
7. Get dataB from brokenkeyspace -> NO DATA

So it seems to have something to do with the "broken" keyspace. I don't know yet how to get
the keyspace into that state. So any input of how I can figure it out or what I could try
would be appreciated.

I have changed the Fix-Version to 1.1.4. 
                
> Commitlog not replayed after restart - data lost
> ------------------------------------------------
>
>                 Key: CASSANDRA-4481
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4481
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.1.2
>         Environment: Single node cluster on 64Bit CentOS
>            Reporter: Ivo Meißner
>            Priority: Critical
>             Fix For: 1.1.4
>
>
> When data is written to the commitlog and I restart the machine, all commited data is
lost that has not been flushed to disk. 
> In the startup logs it says that it replays the commitlog successfully, but the data
is not available then. 
> When I open the commitlog file in an editor I can see the added data, but after the restart
it cannot be fetched from cassandra. 
> {code}
>  INFO 09:59:45,362 Replaying /var/myproject/cassandra/commitlog/CommitLog-83203377067.log
>  INFO 09:59:45,476 Finished reading /var/myproject/cassandra/commitlog/CommitLog-83203377067.log
>  INFO 09:59:45,476 Log replay complete, 0 replayed mutations
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message