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] [Updated] (OAK-3070) Use a lower bound in VersionGC query to avoid checking unmodified once deleted docs
Date Thu, 09 Mar 2017 11:02:38 GMT

     [ https://issues.apache.org/jira/browse/OAK-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marcel Reutegger updated OAK-3070:
----------------------------------
    Attachment: OAK-3070-3.patch

Attached an updated patch [^OAK-3070-3.patch]. The MongoVersionGCSupport does not set a hint
anymore for the query and leaves it up to MongoDB to decide what the best plan is. With the
_modified range now passed to getPossiblyDeletedDocs(), the database is IMO in a better position
to decide what the best index is.

Regarding the query timeout, per default the query on the MongoDB driver level does not have
a timeout. So we should be fine.

> 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
>            Assignee: Vikas Saurabh
>              Labels: performance
>         Attachments: OAK-3070-2.patch, OAK-3070-3.patch, OAK-3070.patch, OAK-3070-updated.patch,
OAK-3070-updated.patch
>
>
> 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.15#6346)

Mime
View raw message