jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-1295) Recovery for missing _lastRev updates
Date Mon, 31 Mar 2014 10:11:14 GMT

    [ https://issues.apache.org/jira/browse/OAK-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955069#comment-13955069

Marcel Reutegger commented on OAK-1295:

I would rather use the current _lastRev on the root document of the current cluster node to
calculate the lower bound.

As for the recovery part, keep in mind that a document may contain changes with a commit root
on the same document as well as changes with a commit root on another document.

> Recovery for missing _lastRev updates
> -------------------------------------
>                 Key: OAK-1295
>                 URL: https://issues.apache.org/jira/browse/OAK-1295
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mongomk
>            Reporter: Marcel Reutegger
>            Assignee: Chetan Mehrotra
>            Priority: Critical
>             Fix For: 0.20
> The _lastRev fields are periodically written to MongoDB with a background thread.
> This means there may be missing _lastRev updates when an Oak instance crashes.
> There must be a recovery mechanism in place when an Oak instance starts up. 
> MongoMK needs to read the most recent _lastRev for the local cluster id and get
> documents with a _modified timestamp at _lastRev or newer. These are candidates
> for missing _lastRev updates. The _lastRev must only be updated for committed
> non-branch changes.

This message was sent by Atlassian JIRA

View raw message