cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6904) commitlog segments may not be archived after restart
Date Thu, 18 Sep 2014 06:50:35 GMT

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

Benedict commented on CASSANDRA-6904:
-------------------------------------

As discussed on CASSANDRA-7965, we could simply archive all commit logs present on restart.
This runs the risk of repeatedly archiving commit logs if we fail repeatedly on restart for
some reason, so may be undesirable. However we can avoid replaying the same CLS twice in 2.1
since we retain the original id in the header.

> commitlog segments may not be archived after restart
> ----------------------------------------------------
>
>                 Key: CASSANDRA-6904
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6904
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jonathan Ellis
>             Fix For: 2.1.1
>
>
> commitlog segments are archived when they are full, so the current active segment will
not be archived on restart (and its contents will not be available for pitr).



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

Mime
View raw message