jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (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:27:51 GMT

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

Alex Parvulescu commented on JCR-3147:
--------------------------------------

I have updated the issue's description and removed the references to low priority tasks.

Tasks submitted by the AbstractIndex will have normal priority, which means they will be executed
asap.
Plus the global executor now benefits from a few dedicated threads that can pickup the work
load immediately (the low priority tasks occupy up to 75% of the threads OOTB).

Marcel, do you think the current tests cover this indexing issue, or would you like to investigate
some more before applying the patch?
                
> 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.

--
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