Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 21 Apr 2014 23:12:17 +0000 (UTC)
From: "Benedict (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12706212.1396454578391.151008.1398121937317@arcas>
In-Reply-To: <JIRA.12706212.1396454578391@arcas>
References: <JIRA.12706212.1396454578391@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-6974) Replaying archived
 commitlogs isn't working
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Benedict edited comment on CASSANDRA-6974 at 4/21/14 11:11 PM:
---------------------------------------------------------------

[~yukim]: seems there is the alternative of being able to create a CF with an explicit UUID?

We probably could treat this differently on replay if we wanted, though. Not sure if it's actually the correct behaviour since CFs could be dropped and recreated deliberately across restores, and we wouldn't be honouring that transition with that change.


was (Author: benedict):
[~yukim]: seems there is the alternative of being able to create a CF with an explicit UUID?

We probably could treat this differently on replay if we wanted, though: not sure if it's actually the correct behaviour

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