cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Florent Clairambault (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-4481) Commitlog not replayed after restart - data lost
Date Wed, 15 Aug 2012 19:01:40 GMT

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

Florent Clairambault edited comment on CASSANDRA-4481 at 8/16/12 6:00 AM:
--------------------------------------------------------------------------

I'm on cassandra 1.1.3.

I have the same problem here on two different keyspaces that I created by different ways at
different times (one with cassandra-cli a year ago and one with the hector library 6 months
ago). I didn't setup any special parameter.

* If some keyspaces don't exist anymore it would be nice to report it somewhere. So that we
could have an idea of what to fix.
* It really doesn't look like these keyspaces don't exist anymore, everything works, including
flushing them. The only thing that doesn't work is replaying logs.

                
      was (Author: superfc):
    I'm on cassandra 1.1.3.

I have the same problem here on two different keyspaces that I created by different way at
different time (one with cassandra-cli and one with the hector library), they were both created
at least 6 months ago and without any special configuration parameter as we're on a single
host (at this point).

* If some keyspaces don't exist anymore it would be nice to report it somewhere. So that we
could have an idea of what to fix.
* It really doesn't look like these keyspaces don't exist anymore, everything works, including
flushing them. The only thing that doesn't work is replaying logs.

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