[
https://issues.apache.org/jira/browse/OAK-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902615#comment-14902615
]
Stefan Egli commented on OAK-3435:
----------------------------------
for logging/debug purpose that could be very useful yes. for the 'discovery
lite' descriptor that information would not be needed. but good to know it is
there!
> 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
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> 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)