[
https://issues.apache.org/jira/browse/CASSANDRA-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943343#comment-13943343
]
Benedict commented on CASSANDRA-6904:
-------------------------------------
To clarify, I think the absolute safest thing to do is to hard-link as soon as
a CL is swapped into active, and then only recycle after an archive operation
is successfully run on the hard-linked version. This should make sure we take
care of not-yet-finished segments (and hence not-yet-archived) on startup as
well, if we push all recycles through this path.
> 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.0.7
>
>
> 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.2#6252)
