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 "Amit Jain (JIRA)" <ji...@apache.org> on 2016/07/25 04:17:21 UTC

[jira] [Closed] (OAK-4563) Specify thread pool name which should be used by Async Indexing task

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

Amit Jain closed OAK-4563.
--------------------------

Bulk Close 1.5.6

> Specify thread pool name which should be used by Async Indexing task
> --------------------------------------------------------------------
>
>                 Key: OAK-4563
>                 URL: https://issues.apache.org/jira/browse/OAK-4563
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>              Labels: docs-impacting
>             Fix For: 1.6, 1.5.6, 1.0.33, 1.4.6, 1.2.18
>
>         Attachments: OAK-4563-v1.patch
>
>
> While running Oak in Sling we rely on Sling Scheduler to ensure that async indexing task are run on leader (OAK-1246) with specified frequency. 
> Be default Sling Scheduler uses a default pool for managing all tasks. It can happen that number of task can be quite hight which can then lead to default thread pool getting exhausted and that causes async indexing to get delayed.
> To ensure that async indexing is not affected by such scenarios we should make use of a dedicated thread pool. This is now supported by SLING-5831



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)