jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3147) AbstractIndex should use the repository executor for indexing tasks
Date Tue, 15 Nov 2011 14:15:52 GMT

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

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

> should we reconsider the patch now?

The indexing tasks in this issue should *not* be low priority. I'm OK with a solution that
uses the repository thread pool, but uses the current thread if the pool is busy.
                
> 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

        

Mime
View raw message