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 "Dominique Jäggi (JIRA)" <ji...@apache.org> on 2017/01/03 09:16:58 UTC

[jira] [Closed] (OAK-5337) LastRevRecoveryAgent should avoid recovering documents from its own cluster id if the instance is running

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

Dominique Jäggi closed OAK-5337.
--------------------------------

bulk close 1.0.36

> LastRevRecoveryAgent should avoid recovering documents from its own cluster id if the instance is running
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: OAK-5337
>                 URL: https://issues.apache.org/jira/browse/OAK-5337
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk
>            Reporter: Vikas Saurabh
>            Assignee: Vikas Saurabh
>             Fix For: 1.5.17, 1.0.36, 1.2.23, 1.4.12, 1.6
>
>         Attachments: OAK-5337.patch
>
>
> In certain scenarios (mostly slow background write leading to lease timeout), last rev recovery agent can kick in and start to recover documents from its own cluster id. The situation is implicitly avoided in 1.4+ (OAK-3397) as the instance would kill itself on lease failure (there are other safeguards too to avoid the situation). But, on older branches, especially 1.0 which has no safeguards, this can lead to loss of last revs.
> All that said, it's anyway reasonable that LRRA shouldn't try to recover its own instance while it's running (startup still needs to be handled by LRRA though).



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