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 "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2014/09/19 14:50:34 UTC

[jira] [Resolved] (OAK-2088) AsyncIndexUpdate can leave orphaned checkpoint in case of abrupt shutdown

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

Alex Parvulescu resolved OAK-2088.
----------------------------------
    Resolution: Fixed

fixed in trunk with rev 1625620. and merged to 1.0 with rev 1625620 and 1625639.

> AsyncIndexUpdate can leave orphaned checkpoint in case of abrupt shutdown
> -------------------------------------------------------------------------
>
>                 Key: OAK-2088
>                 URL: https://issues.apache.org/jira/browse/OAK-2088
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: Chetan Mehrotra
>            Assignee: Alex Parvulescu
>             Fix For: 1.1, 1.0.6
>
>         Attachments: OAK-2088-v2.patch, OAK-2088.patch
>
>
> Currently AsyncIndexUpdate creates a checkpoint with a lifetime of 3
> years. Post index complete the checkpoint is moved to point to revision upto which indexing is done and previous checkpoint is released.
> Now if a system is killed when a index update is in progress particularly in run method where a new checkpoint gets created (Line 229) then that checkpoint would not be released and also would not be recorded in index metadata. Such a checkpoint would prevent GC for a long time.
> http://markmail.org/thread/e4jqkk2malfgjxx6



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