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/05/28 16:19:46 UTC

[jira] [Comment Edited] (OAK-2922) enhance LastRevRecoveryAgent diagnostics

    [ https://issues.apache.org/jira/browse/OAK-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562878#comment-14562878 ] 

Julian Reschke edited comment on OAK-2922 at 5/28/15 2:11 PM:
--------------------------------------------------------------

Note: LastRevRecoveryAgent  already info-logs every 100000 "suspect" nodes; but at least for the RDB case, most time is spent filtering out non-suspects, so this is seldomly triggered.

Seems that to make this useful, the logging would need to happen inside Utils.getSelectedDocuments...


was (Author: reschke):
Note: LastRevRecoveryAgent  already info-logs every 100000 "suspect" nodes; but at least for the RDB case, most time is spent filtering out non-suspects, so this is seldomly triggered.

> enhance LastRevRecoveryAgent diagnostics
> ----------------------------------------
>
>                 Key: OAK-2922
>                 URL: https://issues.apache.org/jira/browse/OAK-2922
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: rdbmk
>    Affects Versions: 1.2.2, 1.0.14, 1.3
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>             Fix For: 1.3.0, 1.2.3, 1.0.15
>
>
> Depending on persistence type and repo size, the LastRevRecoveryAgent might run for a long time. Enhance the logging so that the admin knows what's going on (say, once per minute?).



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