jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Egli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-2556) do intermediate commit during async indexing
Date Mon, 02 Mar 2015 16:29:04 GMT

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

Stefan Egli commented on OAK-2556:
----------------------------------

Agreed. So sunds like a good goal to keep the index consistent within a revision. In the observed
situation the indexer was many revisions behind eg thousands. So maybe we could instead of
'commiting arbitrarily within on diff' try to do multiple index updates between 'narrower
revisions'.. 
I'd say this sounds rather low priority then..

> do intermediate commit during async indexing
> --------------------------------------------
>
>                 Key: OAK-2556
>                 URL: https://issues.apache.org/jira/browse/OAK-2556
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: oak-lucene
>    Affects Versions: 1.0.11
>            Reporter: Stefan Egli
>
> 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
(v6.3.4#6332)

Mime
View raw message