[
https://issues.apache.org/jira/browse/OAK-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354539#comment-14354539
]
Alex Parvulescu commented on OAK-2598:
--------------------------------------
Given the fact that this is controlled by a property in the index definition
'async=async', wouldn't it be easier to tweak the definitions before running
the upgrade and remove the async markers, then post migration you can add them
back in?
Either way, one thing to worry about is the checkpoint reference that the async
indexer uses. if that's missing a reindex will begin, which is definitely not
desirable.
> Provide option to run async index as sync in repository upgrade
> ---------------------------------------------------------------
>
> Key: OAK-2598
> URL: https://issues.apache.org/jira/browse/OAK-2598
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: upgrade
> Reporter: Chetan Mehrotra
> Fix For: 1.1.8, 1.0.13
>
>
> Currently when performing repository upgrade from JR2 to Oak the migration
> logic only runs the synchronous index editors. Async indexes like Lucene/Solr
> are run post migration after the system start.
> Given that migration is a single threaded operation it would at times be
> helpful to allow executing such async indexes in sync mode during migration
> phase. This would avoid rescanning of complete repository again for such
> async indexes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
