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-2556) Intermediate commit during async indexing
Date Thu, 16 Nov 2017 09:18:00 GMT

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

Marcel Reutegger updated OAK-2556:
    Fix Version/s:     (was: 1.8)

> Intermediate commit during async indexing
> -----------------------------------------
>                 Key: OAK-2556
>                 URL: https://issues.apache.org/jira/browse/OAK-2556
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: lucene
>    Affects Versions: 1.0.11
>            Reporter: Stefan Egli
>              Labels: resilience
>             Fix For: 1.10
> A recent issue found at a customer unveils a potential issue with the async indexer.
Reading the AsyncIndexUpdate.updateIndex it looks like it is doing the entire update of the
async indexer *in one go*, ie in one commit.
> When there is - for some reason - however, a huge diff that the async indexer has to
process, the 'one big commit' can become gigantic. There is no limit to the size of the commit
in fact.
> So the suggestion is to do intermediate commits while the async indexer is going on.
The reason this is acceptable is the fact that by doing async indexing, that index is anyway
not 100% up-to-date - so it would not make much of a difference if it would commit after every
100 or 1000 changes either.

This message was sent by Atlassian JIRA

View raw message