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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2019/08/14 12:08:00 UTC

[jira] [Resolved] (OAK-8538) Incomplete recovery on long running merge with branch commits

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

Marcel Reutegger resolved OAK-8538.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.18.0

Fixed in trunk: http://svn.apache.org/r1865110

The recovery process now checks for branch commits that happened before the current {{_lastRev}} and were merged after it. Those are the problematic changes that must be included in the recovery as well.

> Incomplete recovery on long running merge with branch commits
> -------------------------------------------------------------
>
>                 Key: OAK-8538
>                 URL: https://issues.apache.org/jira/browse/OAK-8538
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: documentmk
>    Affects Versions: 1.16.0
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Major
>             Fix For: 1.18.0
>
>
> Recovery of a crashed cluster node that was unable to run a background update after a long running merge with branch commits is incomplete. The recovery will use a start date for the candidate documents that is too recent and not take all the documents of the branch commits into account.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)