[
https://issues.apache.org/jira/browse/OAK-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494392#comment-14494392
]
Chetan Mehrotra commented on OAK-2749:
--------------------------------------
[~edivad] Did not understood about forcing new executor requirement. I think we
just need to add a new scheduled job (possibly provide a config to get such a
job enabled)
Further we would also need to take care on how to do the switch of an existing
index. [~alex.parvulescu] mentioned that if we start a new async index we would
need to take care of checkpoint state also. So we switch an existing index to
say 'async-slow' then we would also need to bootstrap the checkpoint state
otherwise it would trigger a full reindex.
Also I am not sure if we would should allow such task to run in parallel or
ensure at a time one indexer is running (so as to not put load)
[~alex.parvulescu] Thoughts?
> Provide a "different lane" for slow indexers in async indexing
> --------------------------------------------------------------
>
> Key: OAK-2749
> URL: https://issues.apache.org/jira/browse/OAK-2749
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Davide Giannella
> Assignee: Davide Giannella
> Fix For: 1.3.0
>
> Attachments: OAK-2749-rc1.diff
>
>
> In case of big repositories, asynchronous index like Lucene Property,
> could lag behind as slow indexes, for example Full Text, are taken
> care in the same thread pool.
> Provide a separate thread pool in which such indexes could be
> registered.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
