[
https://issues.apache.org/jira/browse/OAK-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940720#comment-16940720
]
Marcel Reutegger commented on OAK-8648:
---------------------------------------
bq. ...or a new cluster id is used, right?
No, there shouldn't be any initial sweep when a new clusterId is created. In
that case the sweep revision for the new clusterId is set to the initial head
revision on startup.
You can somewhat construct a case where the implementation will still run an
initial sweep, when an clusterId entry created by a pre 1.8 version is manually
removed. The implementation will run an initial sweep when the clusterId is
resurrected. This is because the decision whether an initial sweep is necessary
is not based on the data in the clusterNodes collection, but based on the data
in the root document where the sweep revisions are located.
> 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
> 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)
