[jira] [Updated] (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 ] Chetan Mehrotra updated OAK-4563: - Labels: docs-impacting (was: candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4 docs-impacting) Fix Version/s: 1.2.18 1.4.6 1.0.33 Merged to branches * 1.0 - [1753462|http://svn.apache.org/r1753462] * 1.2 - [1753461|http://svn.apache.org/r1753461] * 1.4 - [1753460|http://svn.apache.org/r1753460] > 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)
[jira] [Updated] (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 ] Chetan Mehrotra updated OAK-4563: - Labels: candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4 docs-impacting (was: candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4) > 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, > docs-impacting > Fix For: 1.6, 1.5.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)
[jira] [Updated] (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 ] 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)
[jira] [Updated] (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 ] Chetan Mehrotra updated OAK-4563: - 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 was: While running Oak in Sling we rely on Sling Scheduler to ensure that async indexing task are run on leader 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 > 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 > > > 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)
[jira] [Updated] (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 ] Chetan Mehrotra updated OAK-4563: - Labels: candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4 (was: ) > 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 > > > 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)
