You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2018/03/08 15:05:00 UTC

[jira] [Commented] (OAK-4943) Keep Lucene Commits so that if the Segments file gets corrupted recovery can be attempted.

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

Thomas Mueller commented on OAK-4943:
-------------------------------------

[~chetanm] [~ianeboston] no work was done on this issue for a long time... Do you want to keep it open, or is it OK to close it as won't fix?

> Keep Lucene Commits so that if the Segments file gets corrupted recovery can be attempted.
> ------------------------------------------------------------------------------------------
>
>                 Key: OAK-4943
>                 URL: https://issues.apache.org/jira/browse/OAK-4943
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: lucene
>    Affects Versions: 1.6.0
>            Reporter: Ian Boston
>            Assignee: Chetan Mehrotra
>            Priority: Major
>
> Currently, Lucene deletes all previous generations of the segments files as it has it uses the default IndexDeletionPolicy. Changing this to an IndexDeletionPolicy that keeps a number of previous segments files will allow an operator to find the most recent valid commit when the current segments file reports corruption. The patch found at https://github.com/apache/jackrabbit-oak/compare/trunk...ieb:KeepLuceneCommits keeps 10 previous commits.
> A more sophisticated policy could be used to save commits non-linearly over time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)