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 2019/12/12 12:40:00 UTC
[jira] [Comment Edited] (OAK-8648) Log reason why
NodeDocumentSweeper.sweep is called
[ https://issues.apache.org/jira/browse/OAK-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978357#comment-16978357 ]
Julian Reschke edited comment on OAK-8648 at 12/12/19 12:39 PM:
----------------------------------------------------------------
trunk: (1.20.0) [r1867763|http://svn.apache.org/r1867763]
1.10: (1.10.7) [r1870050|http://svn.apache.org/r1870050]
1.8: [r1871269|http://svn.apache.org/r1871269]
was (Author: reschke):
trunk: (1.20.0) [r1867763|http://svn.apache.org/r1867763]
1.10: [r1870050|http://svn.apache.org/r1870050]
> Log reason why NodeDocumentSweeper.sweep is called
> --------------------------------------------------
>
> Key: OAK-8648
> URL: https://issues.apache.org/jira/browse/OAK-8648
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
> Affects Versions: 1.8.9
> Reporter: Vincent Frey
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 1.20.0, 1.10.7, 1.8.19
>
> Attachments: OAK-8648.diff
>
>
> It can happen during a cluster node restart, that a NodeDocumentSweeper.sweep is triggered.
> Depending on the number of nodes, this can delay the start process for several hours.
> In order to understand what caused the sweep, it could be interesting to log (INFO level) the reason why it has been triggered.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)