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

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.0.33, 1.2.18, 1.4.6, 1.5.6, 1.6.0
• Component/s: core
• Labels: docs-impacting
• Assignee: Chetan Mehrotra
• Reporter: Chetan Mehrotra
• Created: 15/Jul/16 08:36
• Updated: 25/Jul/16 04:17
• Resolved: 20/Jul/16 05:35

Description

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

Issue Links

• relates to: OAK-1246 Make AsynchIndexUpdate task to run only on a single node in a cluster
• relates to: SLING-5831 Support different thread pools for scheduled tasks