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 "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2017/10/24 23:34:00 UTC

[jira] [Resolved] (OAK-6864) IndexUpdate should disable superseded indexes only during an async cycle run

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

Vikas Saurabh resolved OAK-6864.
--------------------------------
    Resolution: Fixed

Fixed on trunk at [r1813242|https://svn.apache.org/r1813242].

> IndexUpdate should disable superseded indexes only during an async cycle run
> ----------------------------------------------------------------------------
>
>                 Key: OAK-6864
>                 URL: https://issues.apache.org/jira/browse/OAK-6864
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: indexing
>    Affects Versions: 1.7.10
>            Reporter: Vikas Saurabh
>            Assignee: Vikas Saurabh
>            Priority: Minor
>             Fix For: 1.8, 1.7.11
>
>
> Once an superseding index is indexed (has {{:disableIndexesOnNextCycle}} flag) then IndexUpdate disables the superseded index the next time superseding index is indexed. So, if we have and async index running in nrt mode too - then nrt updates also disable indexes.
> We should have a more controlled disabling action (apart from concurrent nrt/sync updates would likely conflict with each to fail the commit) - do it in async cycle.
> Note: This is only relevant when superseding index is an async index - superseding sync indexes would continue to work as earlier.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)