[
https://issues.apache.org/jira/browse/OAK-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-2749:
----------------------------------
Attachment: OAK-2749-rc2.diff
[~chetanm] in [^OAK-2749-rc2.diff] I reverted the forcing of new
executor. If you could give a look to see if everything is in place it
would be awesome.
{quote}
Or we can simply expose a JMX opertaion to perform this sort of migration
{quote}
I'll have a look at the JMX thing. Will follow up here once I have a
more detailed understanding of what we should do.
> 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, OAK-2749-rc2.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)
