[
http://jira.codehaus.org/browse/MRM-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MRM-1439.
-----------------------------
Resolution: Fixed
Fix Version/s: 1.3.3
Assignee: Brett Porter
The problem was that each request re-scanned the index to see if the document
was an addition or an update. As the size of the index grew, each indexing task
became larger, causing the queue to grow exponentially.
With the fix in place, the queue should now not grow above 5-10 items when
operating normally, and should complete a full scan in about 1/3rd of the time.
> improve indexing performance
> ----------------------------
>
> Key: MRM-1439
> URL: http://jira.codehaus.org/browse/MRM-1439
> Project: Archiva
> Issue Type: Improvement
> Components: indexing
> Affects Versions: 1.3.2
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.3.3
>
>
> we've observed when indexing a large repository, that over time a large
> number of index requests fill up the queue, consuming both memory and disk
> processing. If there is not enough memory allocated, the server can
> eventually restart, and the indexing will not complete, meaning the queue
> will fill up again on restart.
> This is not a memory leak - if the queue completes all operates as normal.
> The problem is the queue not being processed quickly enough.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
