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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2014/01/21 11:26:21 UTC
[jira] [Updated] (OAK-1295) Recovery for missing _lastRev updates
[ https://issues.apache.org/jira/browse/OAK-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated OAK-1295:
----------------------------------
Fix Version/s: (was: 0.15)
0.16
> 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
> Fix For: 0.16
>
>
> 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
(v6.1.5#6160)