You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (Commented) (JIRA)" <ji...@apache.org> on 2011/11/15 13:37:52 UTC

[jira] [Commented] (JCR-3147) AbstractIndex should use the repository executor for indexing tasks

    [ https://issues.apache.org/jira/browse/JCR-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150430#comment-13150430 ] 

Marcel Reutegger commented on JCR-3147:
---------------------------------------

The usage of DynamicPooledExecutor in AbstractIndex is a bit special because it is not meant to execute tasks at some point in the future, but just parallelize a number of tasks given the number of available cores. It is important that the tasks are scheduled and executed rather immediately. Otherwise the current transaction will be delayed unnecessarily.
                
> AbstractIndex should use the repository executor for indexing tasks
> -------------------------------------------------------------------
>
>                 Key: JCR-3147
>                 URL: https://issues.apache.org/jira/browse/JCR-3147
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Alex Parvulescu
>            Priority: Minor
>         Attachments: JCR-3147.patch
>
>
> The AbstractIndex still uses its own executor for indexing tasks, it should switch to the global repository executor.
> It should also mark the tasks as 'low priotiry' as soon as JCR-3146 gets into the trunk.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira