Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 17 Sep 2014 22:35:34 +0000 (UTC)
From: "Benedict (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12742299.1410992941000.60769.1410993334023@Atlassian.JIRA>
In-Reply-To: <JIRA.12742299.1410992941000@Atlassian.JIRA>
References: <JIRA.12742299.1410992941000@Atlassian.JIRA>
 <JIRA.12742299.1410992941343@arcas>
Subject: [jira] [Commented] (CASSANDRA-7965) Active commit log doesn't get
 archived on Cassandra restart
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Benedict commented on CASSANDRA-7965:
-------------------------------------

In practice it could be any CL that hasn't already been recycled. We should trigger an archive of every existing file on startup.

> Active commit log doesn't get archived on Cassandra restart
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-7965
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7965
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Max Barnash
>
> After a restart Cassandra replays and recycles all present commit logs. Because active commit log never gets archived, we lose some of the data from the archives.
> One of the ways to fix this would be archiving all commit logs at startup before replaying and recycling them.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)