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 "Julian Reschke (JIRA)" <ji...@apache.org> on 2015/09/22 23:43:05 UTC
[jira] [Resolved] (OAK-3435)
LastRevRecoveryAgent/MissingLastRevSeeker improvements
[ https://issues.apache.org/jira/browse/OAK-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved OAK-3435.
---------------------------------
Resolution: Fixed
trunk: http://svn.apache.org/r1704670
1.2: http://svn.apache.org/r1704684
1.0: http://svn.apache.org/r1704734
> LastRevRecoveryAgent/MissingLastRevSeeker improvements
> ------------------------------------------------------
>
> Key: OAK-3435
> URL: https://issues.apache.org/jira/browse/OAK-3435
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, mongomk, rdbmk
> Affects Versions: 1.0.21, 1.3.6, 1.2.6
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Fix For: 1.3.7, 1.2.7
>
> Attachments: OAK-3435.diff
>
>
> In order to make debugging easier, we should:
> - log exceptions that occur while updating the cluster node info entries
> - when we mark an entry as being recovered, record which cluster node is running the recovery
> - avoid the conditional race condition mentioned in the code comment for acquireRecoveryLock
> - improve logging for cluster node infos that match the current instance id but for some reason will not be recovered
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)