You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/12/09 05:06:59 UTC
[jira] Commented: (MRM-1260) Indexing tasks are lost when server
goes down or re-starts
[ http://jira.codehaus.org/browse/MRM-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246957#action_246957 ]
Brett Porter commented on MRM-1260:
-----------------------------------
conversely, if an initial scan doesn't complete the whole thing starts again rather than skipping over things that are already scanned because it may need to index them again. Better tracking of these tasks would be good to have.
> Indexing tasks are lost when server goes down or re-starts
> ----------------------------------------------------------
>
> Key: MRM-1260
> URL: http://jira.codehaus.org/browse/MRM-1260
> Project: Archiva
> Issue Type: Bug
> Components: indexing
> Affects Versions: 1.2.2
> Reporter: Maria Odea Ching
> Fix For: Backlog
>
>
> Queued indexing tasks are lost when the server goes down or re-starts resulting to some artifacts not being indexed. The workaround is to force Archiva to scan the entire repository again when the server is back online.
--
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