jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chetan Mehrotra (JIRA)" <j...@apache.org>
Subject [jira] [Created] (OAK-3070) Use a lower bound in VersionGC query to avoid checking unmodified once deleted docs
Date Thu, 02 Jul 2015 17:59:04 GMT
Chetan Mehrotra created OAK-3070:
------------------------------------

             Summary: Use a lower bound in VersionGC query to avoid checking unmodified once
deleted docs
                 Key: OAK-3070
                 URL: https://issues.apache.org/jira/browse/OAK-3070
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: mongomk, rdbmk
            Reporter: Chetan Mehrotra
             Fix For: 1.3.5


As part of OAK-3062 [~mreutegg] suggested

{quote}
As a further optimization we could also limit the lower bound of the _modified
range. The revision GC does not need to check documents with a _deletedOnce
again if they were not modified after the last successful GC run. If they
didn't change and were considered existing during the last run, then they
must still exist in the current GC run. To make this work, we'd need to
track the last successful revision GC run. 
{quote}

Lowest last validated _modified can be possibly saved in settings collection and reused for
next run



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message