You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ryan McGuire (JIRA)" <ji...@apache.org> on 2014/04/03 18:30:17 UTC

[jira] [Comment Edited] (CASSANDRA-6974) Replaying archived commitlogs isn't working

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

Ryan McGuire edited comment on CASSANDRA-6974 at 4/3/14 4:28 PM:
-----------------------------------------------------------------

Yes, the backup location is cleared each run (it's a new temp directory each time the script runs.)

The multiple runs you are seeing in the log file is part of the script itself, it creates the initial commitlogs, blows away the schema, shutsdown, edits the commitlog_archive.properties file, then starts back up. It's on the second startup that it tries to replay the archived commitlogs, and it's failing there.


was (Author: enigmacurry):
Yes, the backup location is cleared each run (it's a new temp directory each time the script runs.)

The multiple runs you are seeing in the log file is part of the script itself, it creates the initial commitlogs, blows away the schema, shutsdown, edits the commitlog_archive.properties file, then starts back up.

> Replaying archived commitlogs isn't working
> -------------------------------------------
>
>                 Key: CASSANDRA-6974
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6974
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Ryan McGuire
>            Assignee: Benedict
>             Fix For: 2.1 beta2
>
>         Attachments: 2.0.system.log, 2.1.system.log
>
>
> I have a test for restoring archived commitlogs, which is not working in 2.1 HEAD.  My commitlogs consist of 30,000 inserts, but system.log indicates there were only 2 mutations replayed:
> {code}
> INFO  [main] 2014-04-02 11:49:54,173 CommitLog.java:115 - Log replay complete, 2 replayed mutations
> {code}
> There are several warnings in the logs about bad headers and invalid CRCs: 
> {code}
> WARN  [main] 2014-04-02 11:49:54,156 CommitLogReplayer.java:138 - Encountered bad header at position 0 of commit log /tmp/dtest
> -mZIlPE/test/node1/commitlogs/CommitLog-4-1396453793570.log, with invalid CRC. The end of segment marker should be zero.
> {code}
> compare that to the same test run on 2.0, where it replayed many more mutations:
> {code}
>  INFO [main] 2014-04-02 11:49:04,673 CommitLog.java (line 132) Log replay complete, 35960 replayed mutations
> {code}
> I'll attach the system logs for reference.
> [Here is the dtest to reproduce this|https://github.com/riptano/cassandra-dtest/blob/master/snapshot_test.py#L75] - (This currently relies on the fix for snapshots available in CASSANDRA-6965.)



--
This message was sent by Atlassian JIRA
(v6.2#6252)