[
https://issues.apache.org/jira/browse/OAK-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-5553:
----------------------------------
Fix Version/s: (was: 1.12.0)
> Index async index in a new lane without blocking the main lane
> --------------------------------------------------------------
>
> Key: OAK-5553
> URL: https://issues.apache.org/jira/browse/OAK-5553
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: indexing
> Reporter: Chetan Mehrotra
> Priority: Major
> Fix For: 1.14.0
>
>
> Currently if an async index has to be reindex for any reason say update of
> index definition then this process blocks the indexing of other indexes on
> that lane.
> For e.g. if on "async" lane we have 2 indexes /oak:index/fooIndex and
> /oak:index/barIndex and fooIndex needs to be reindexed. In such a case
> currently AsyncIndexUpdate would work on reindexing and untill that gets
> complete other index do not receive any update. If the reindexing takes say 1
> day then other index would start lagging behind by that time. Note that NRT
> indexing would help somewhat here.
> To improve this we can implement something similar to what was done for
> property index in OAK-1456 i.e. provide a way where
> # an admin can trigger reindex of some async indexes
> # those indexes are moved to different lane and then reindexed
> # post reindexing logic should then move them back to there original lane
> Further this task can then be performed on non leader node as the indexes
> would not be part of any active lane. Also we may implement it as part of
> oak-run
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
