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/07/29 06:32:06 UTC
[jira] [Closed] (OAK-8449) LastRev check/fix in DocumentNodeStore
MBean
[ https://issues.apache.org/jira/browse/OAK-8449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke closed OAK-8449.
-------------------------------
> LastRev check/fix in DocumentNodeStore MBean
> --------------------------------------------
>
> Key: OAK-8449
> URL: https://issues.apache.org/jira/browse/OAK-8449
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: documentmk
> Reporter: Vinod Holani
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 1.16.0
>
> Attachments: OAK-8449_1.patch, OAK-8449_2.patch
>
>
> There is existing tooling to check _lastRev consistency of documents in the DocumentStore. Some of the tooling is limited to MongoDB because it is implemented as utility functions for the MongoDB shell ([oak-mongo.js|https://jackrabbit.apache.org/oak/docs/oak-mongo-js/oak.html]). The oak-run [recovery|https://github.com/apache/jackrabbit-oak/tree/trunk/oak-run#recovery-mode] command was initially only available on MongoDB as well, but recently RDB support was added (OAK-8004). The recovery command however has some drawbacks. It scans the entire nodes collection, which can be a rather expensive operation and when started in read-write mode.
> This improvement is about adding _lastRev check and fix functionality to the DocumentNodeStore MBean. The scope of the check and fix would be limited to some path(s) in order to keep the runtime of the operation low.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)