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 07:47:02 GMT

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

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

I can reproduce the bug as follows:

1. I insert data with my client into a column family.
2. When I select the data afterwards with a cassandra client, the data is returned.
{code}
get comment['1|3488da80-1dd5-11b2-aff8-030772c33eed'];
=> (super_column=34942d20-1dd5-11b2-bfef-3f53095dd669,
     (column=added, value=1343979036, timestamp=1343979036707674)
     (column=id, value=34942d20-1dd5-11b2-bfef-3f53095dd669, timestamp=1343979036707674)
     (column=itemId, value=3488da801dd511b2aff8030772c33eed, timestamp=1343979036707674)
     (column=text, value=Comment, timestamp=1343979036707674)
     (column=typeId, value=1, timestamp=1343979036707674)
     (column=userId, value=4ab5fcb6753a8021ae02, timestamp=1343979036707674))
Returned 1 results.
Elapsed time: 6 msec(s).
{code}
3. Then I restart the machine
4. When I start cassandra again, I get the following output 
{code}
 INFO 09:33:56,857 Log replay complete, 0 replayed mutations
{code}
5. I select the exact same row and get no results, so the data I inserted before is gone.
{code}
get comment['1|3488da80-1dd5-11b2-aff8-030772c33eed'];
Returned 0 results.
Elapsed time: 120 msec(s).
{code}

I tried to reproduce it with a newly created keyspace and column family and wasn't able to
reproduce it yet. In the other keyspace I can reproduce it consistently and it happens on
all column familys. 
Any suggestions what I can try to narrow it down?
                
> 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.3
>
>
> 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