jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chetan Mehrotra (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-4563) Specify thread pool name which should be used by Async Indexing task
Date Tue, 19 Jul 2016 05:36:20 GMT

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

Chetan Mehrotra updated OAK-4563:
---------------------------------
    Attachment: OAK-4563-v1.patch

[initial patch|^OAK-4563-v1.patch] for the same

Also started a thread for usage in Oak http://jackrabbit-oak.markmail.org/thread/a7vizo556ceyl7er

> 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: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4
>             Fix For: 1.6
>
>         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)

Mime
View raw message