jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vikas Saurabh (JIRA)" <j...@apache.org>
Subject [jira] [Created] (OAK-5337) LastRevRecoveryAgent should avoid recovering documents from its own cluster id if the instance is running
Date Mon, 19 Dec 2016 21:40:58 GMT
Vikas Saurabh created OAK-5337:
----------------------------------

             Summary: 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


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)

Mime
View raw message