jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-1856) Change value for SearchIndex#DEFAULT_EXTRACTOR_BACK_LOG
Date Fri, 14 Nov 2008 10:34:44 GMT

     [ https://issues.apache.org/jira/browse/JCR-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Marcel Reutegger resolved JCR-1856.

       Resolution: Fixed
    Fix Version/s: 1.6.0

Changed in revision: 713971

> Change value for SearchIndex#DEFAULT_EXTRACTOR_BACK_LOG
> -------------------------------------------------------
>                 Key: JCR-1856
>                 URL: https://issues.apache.org/jira/browse/JCR-1856
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.6.0
> The value is currently 100. This means that once 100 extractor jobs are pending in the
indexing queue additional extractor jobs are executed with the current thread. I think it
would be more useful to change this value to Integer.MAX_VALUE (or in other words: unbounded).
> If the backlog is filled up then this indicates that the repository is very busy and
we should not put additional burden on the current thread in that case.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message