[
https://issues.apache.org/jira/browse/CASSANDRA-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14142983#comment-14142983
]
Benedict commented on CASSANDRA-6904:
-------------------------------------
In 2.1 we should be using the header information to ensure we only replay each
segment once.
I also think this is a good opportunity in 2.1 to drop in support for native
archival, with which we could easily avoid backing up twice. The current
situation feels a little clunky to me, since if we have a bug or other problem
causing startup to crash we might repeatedly fill up the archive disk without
the operator realising. That could be a follow up ticket, I'm fine either way,
but it's really not a very challenging feature to insert and helps make this
much more sane.
> 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
> Assignee: Sam Tunnicliffe
> Fix For: 2.0.11, 2.1.1
>
> Attachments: 2.0-6904.txt, 2.1-6904.txt
>
>
> 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)
