[jira] [Updated] (CASSANDRA-6904) commitlog segments may not be archived after restart

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-6904:
--------------------------------------

    Assignee:     (was: Jonathan Ellis)
     Summary: commitlog segments may not be archived after restart  (was: partially full commitlog segments are not archived after restart)

actually it's not just the current active segment; it could include any other segments for which archive is not complete at restart time.  No state is kept by the segment manager to record which have been archived and which have not.

Keeping this state in a system table would have the obvious problem that you need to replay the CL before you know which segments have not been archived yet.  (because of how pitr works, it would be much better to be able to archive before replaying.)  So it's a tough problem to solve.

/cc [~vijay2win@yahoo.com]

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