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:57:55 GMT

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

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

> Marcel, do you think the current tests cover this indexing issue

Probably not. To me it is not clear how the system will behave when the pool is busy with
index merges and then additional tasks like these in the AbstractIndex are added. I guess
the save would be blocked for a while until a thread is available again. This is a slightly
different behaviour than before.
                
> 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