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/11/25 06:29:06 UTC

[jira] [Closed] (OAK-8648) Log reason why NodeDocumentSweeper.sweep is called

     [ https://issues.apache.org/jira/browse/OAK-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke closed OAK-8648.
-------------------------------

> 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
>              Labels: candidate_oak_1_8
>             Fix For: 1.20.0, 1.10.7
>
>         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)