[
https://issues.apache.org/jira/browse/OAK-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved OAK-6858.
-----------------------------------
Resolution: Invalid
Fix Version/s: (was: 1.8)
There already is progress logging. Log message look like these:
{noformat}
24.10.2017 13:12:40.928 *INFO* [FelixStartLevel]
org.apache.jackrabbit.oak.plugins.document.NodeDocumentSweeper Checked 100000
documents so far
24.10.2017 13:12:49.938 *INFO* [FelixStartLevel]
org.apache.jackrabbit.oak.plugins.document.NodeDocumentSweeper Checked 200000
documents so far
24.10.2017 13:12:59.147 *INFO* [FelixStartLevel]
org.apache.jackrabbit.oak.plugins.document.NodeDocumentSweeper Checked 300000
documents so far
24.10.2017 13:13:11.029 *INFO* [FelixStartLevel]
org.apache.jackrabbit.oak.plugins.document.NodeDocumentSweeper Checked 400000
documents so far
{noformat}
Resolving as INVALID.
> Log revision sweep progress on startup
> --------------------------------------
>
> Key: OAK-6858
> URL: https://issues.apache.org/jira/browse/OAK-6858
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
>
> The DocumentNodeStore should log progress of the revision sweep operation
> when it runs on startup. This is a one-time operation that is triggered when
> Oak is upgraded to 1.8 or newer. Ideally, the revision sweep is done with
> oak-run as part of a coordinated cluster upgrade as documented here:
> https://jackrabbit.apache.org/oak/docs/nodestore/document/upgrade.html
> For cases where the sweep is not performed with oak-run, the implementation
> should write log messages why startup takes longer than usual and also
> provide progress messages.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
