[ 
https://jira.codehaus.org/browse/MRM-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brett Porter reassigned MRM-1588:
---------------------------------

    Assignee: Brett Porter
    
> repository statistics time has blown out again
> ----------------------------------------------
>
>                 Key: MRM-1588
>                 URL: https://jira.codehaus.org/browse/MRM-1588
>             Project: Archiva
>          Issue Type: Bug
>          Components: Metadata Repository
>    Affects Versions: 1.4-M2
>            Reporter: Brett Porter
>            Assignee: Brett Porter
>
> This may be the cause of the failures / hangs I've been seeing. In my local 
> environment:
> {code}
> 2012-01-16 10:02:18,487 [pool-2-thread-1] INFO  
> org.apache.archiva.metadata.repository.stats.DefaultRepositoryStatisticsManager
>   - Gathering statistics executed in 3366961ms
> {code}
> For repo:
> {code}
> .\ Scan of internal \.__________________________________________
>   Repository Dir    : /Users/brett/Library/Application 
> Support/Archiva/data/repositories/internal
>   Repository Name   : Archiva Managed Internal Repository
>   Repository Layout : default
>   Known Consumers   : (7 configured)
>                       create-missing-checksums
>                       auto-remove
>                       auto-rename
>                       repository-purge (Total: 263501ms; Avg.: 17; Count: 
> 14904)
>                       index-content (Total: 0ms; Avg.: 0; Count: 1)
>                       create-archiva-metadata
>                       duplicate-artifacts (Total: 2339ms; Avg.: 2339; Count: 
> 1)
>   Invalid Consumers : <none>
>   Duration          : 13 Minutes 5 Seconds 169 Milliseconds
>   When Gathered     : 1/16/12 9:06 AM
>   Total File Count  : 72758
>   Avg Time Per File : 10 Milliseconds
> ______________________________________________________________
> {code}
> This was a longer scan than usual, typically <1 - 2 minutes, but the 
> statistics scans have been ~30mins then too.
> Also worth noting that the purge seems to be triggering each time but not 
> affecting those files.
> I'll look into both.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to