Hi Brett,
this is the output.
Am 08.02.2011 09:46, schrieb Brett Porter:
> There was an issue before 1.3.3 about this at the end of a scan that should
> have been fixed. Do you get anything after the last horizontal rule?
>
That's the log of the last hour.
2011-02-08 08:59:57,182 [btpool0-0] INFO
com.opensymphony.xwork2.validator.Action
ValidatorManagerFactory - Detected AnnotationActionValidatorManager,
initializing
it...
2011-02-08 09:00:00,105 [pool-2-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaRepositoryScanningTaskExecutor - Executing task from
queue with
job name: RepositoryTask [repositoryId=snapshots, resourceFile=null,
scanAll=fals
e, updateRelatedArtifacts=false]
2011-02-08 09:00:00,105 [pool-1-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaDatabaseUpdateTaskExecutor - Executing task from
queue with job
name: DatabaseTask
2011-02-08 09:00:00,145 [pool-2-thread-1] INFO
org.apache.maven.archiva.repositor
y.scanner.RepositoryScannerInstance - Walk Started: [snapshots]
/data/archiva/rep
ositories/snapshots
2011-02-08 09:00:00,157 [pool-1-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaDatabaseUpdateTaskExecutor - Task: Updating
unprocessed artifac
ts
2011-02-08 09:00:00,440 [pool-1-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaDatabaseUpdateTaskExecutor - Task: Updating processed
artifacts
2011-02-08 09:00:12,904 [pool-2-thread-1] INFO
org.apache.maven.archiva.repositor
y.scanner.RepositoryScannerInstance - Walk Finished: [snapshots]
/data/archiva/re
positories/snapshots
2011-02-08 09:00:12,905 [pool-2-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaRepositoryScanningTaskExecutor - Finished repository
task:
.\ Scan of snapshots \.__________________________________________
Repository Dir : /data/archiva/repositories/snapshots
Repository Name : Archiva Managed Snapshot Repository
Repository Layout : default
Known Consumers : (1 configured)
update-db-artifact
Invalid Consumers : <none>
Duration : 12 Seconds 759 Milliseconds
When Gathered : 08.02.11 09:00
Total File Count : 22879
Avg Time Per File :
______________________________________________________________
2011-02-08 09:00:20,013 [pool-2-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaRepositoryScanningTaskExecutor - Executing task from
queue with
job name: RepositoryTask [repositoryId=internal, resourceFile=null,
scanAll=false
, updateRelatedArtifacts=false]
2011-02-08 09:00:20,312 [pool-2-thread-1] INFO
org.apache.maven.archiva.repositor
y.scanner.RepositoryScannerInstance - Walk Started: [internal]
/data/archiva/repo
sitories/internal
2011-02-08 09:00:30,248 [pool-2-thread-1] INFO
org.apache.maven.archiva.repositor
y.scanner.RepositoryScannerInstance - Walk Finished: [internal]
/data/archiva/rep
ositories/internal
2011-02-08 09:00:30,248 [pool-2-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaRepositoryScanningTaskExecutor - Finished repository
task:
.\ Scan of internal \.__________________________________________
Repository Dir : /data/archiva/repositories/internal
Repository Name : Archiva Managed Internal Repository
Repository Layout : default
Known Consumers : (1 configured)
update-db-artifact
Invalid Consumers : <none>
Duration : 9 Seconds 936 Milliseconds
When Gathered : 08.02.11 09:00
Total File Count : 55540
Avg Time Per File :
______________________________________________________________
2011-02-08 09:00:51,418 [pool-1-thread-1] INFO
org.apache.maven.archiva.scheduled
.executors.ArchivaDatabaseUpdateTaskExecutor - Finished database task
in 51261ms.
> It might be that your index is very large (though it shouldn't be for these
> repository sizes). What is the size of the .index and .indexer directories?
du -hs .index
9.0M .index
du -hs .indexer/
9.5M .indexer/
>
> What do you see on the system status page during the high CPU usage?
Administration - System Status
Queues
Queue Size
database-update 0
indexing 0
repository-scanning 0
Repository Scans Currently in Progress
No scans in progress.
Caches
Cache Size Hits Misses Hit Ratio
operations 25 11 50 18% Flush
users 8 254 21 92% Flush
resources 2 2 4 33% Flush
url-failures-cache 186 0 0 0% Flush
userPermissions 2 249 12 95% Flush
effective-project-cache 102 233705 102 100% Flush
roles 13 4 26 13% Flush
permissions 31 14 62 18% Flush
effectiveRoleSet 0 0 0 0% Flush
userAssignments 0 2 4 33% Flush
ehcache 0 0 0 0% Flush
keys 1 0 4 0% Flush
Memory Usage
48M/144M (Max: 991M)
Current Time
Tue Feb 08 09:43:11 CET 2011
>
> Thanks,
> Brett
>
Thanks,
Benjamin
> On 08/02/2011, at 7:13 PM, Benjamin Knoth wrote:
>
>>
> Hi all,
> we use Archiva and we have problems with our cpu usage.
> If i restart archiva everything is running fine. After 3-6 hours the
> java process of archiva use 100% of the cpu from one to the next
> moment. We had this problem on Archiva 1.3.1 and 1.3.3. On Archiva
> 1.3.1 it came after the 3-5 times where the db artefacts were updated.
> The snapshot repository need 12 minutes. I deleted some snapshots.
> Lasst week we updated it to 1.3.3 and now i can't find something
> important on log. On the last 100% usage problem i got a message from
> nagios the usage of cpu is critcal at 7:43 o'clock, but in the log i
> found only this messages.
>
> 2011-02-08 07:00:13,123 [pool-2-thread-1] INFO
> org.apache.maven.archiva.repositor
> y.scanner.RepositoryScannerInstance - Walk Started: [snapshots]
> /data/archiva/rep
> ositories/snapshots
> 2011-02-08 07:00:15,778 [pool-1-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaDatabaseUpdateTaskExecutor - Task: Updating
> processed artifacts
> 2011-02-08 07:00:18,778 [pool-2-thread-1] INFO
> org.apache.maven.archiva.repositor
> y.scanner.RepositoryScannerInstance - Walk Finished: [snapshots]
> /data/archiva/re
> positories/snapshots
> 2011-02-08 07:00:18,778 [pool-2-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaRepositoryScanningTaskExecutor - Finished
> repository task:
> .\ Scan of snapshots \.__________________________________________
> Repository Dir : /data/archiva/repositories/snapshots
> Repository Name : Archiva Managed Snapshot Repository
> Repository Layout : default
> Known Consumers : (1 configured)
> update-db-artifact (Total: 2592ms; Avg.: 1296;
> Count: 2)
> Invalid Consumers : <none>
> Duration : 5 Seconds 654 Milliseconds
> When Gathered : 2/8/11 7:00 AM
> Total File Count : 22879
> Avg Time Per File :
> ______________________________________________________________
> 2011-02-08 07:00:49,254 [pool-1-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaDatabaseUpdateTaskExecutor - Finished database task
> in 49230ms.
> 2011-02-08 08:00:00,022 [pool-1-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaDatabaseUpdateTaskExecutor - Executing task from
> queue with job
> name: DatabaseTask
> 2011-02-08 08:00:00,022 [pool-1-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaDatabaseUpdateTaskExecutor - Task: Updating
> unprocessed artifac
> ts
> 2011-02-08 08:00:00,046 [pool-2-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaRepositoryScanningTaskExecutor - Executing task
> from queue with
> job name: RepositoryTask [repositoryId=internal, resourceFile=null,
> scanAll=false
> , updateRelatedArtifacts=false]
> 2011-02-08 08:00:00,119 [pool-2-thread-1] INFO
> org.apache.maven.archiva.repositor
> y.scanner.RepositoryScannerInstance - Walk Started: [internal]
> /data/archiva/repo
> sitories/internal
> 2011-02-08 08:00:02,229 [pool-1-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaDatabaseUpdateTaskExecutor - Task: Updating
> processed artifacts
> 2011-02-08 08:00:10,753 [pool-2-thread-1] INFO
> org.apache.maven.archiva.repositor
> y.scanner.RepositoryScannerInstance - Walk Finished: [internal]
> /data/archiva/rep
> ositories/internal
> 2011-02-08 08:00:10,753 [pool-2-thread-1] INFO
> org.apache.maven.archiva.scheduled
> .executors.ArchivaRepositoryScanningTaskExecutor - Finished
> repository task:
> .\ Scan of internal \.__________________________________________
> Repository Dir : /data/archiva/repositories/internal
> Repository Name : Archiva Managed Internal Repository
> Repository Layout : default
> Known Consumers : (1 configured)
> update-db-artifact
> Invalid Consumers : <none>
> Duration : 10 Seconds 634 Milliseconds
> When Gathered : 2/8/11 8:00 AM
> Total File Count : 55540
> Avg Time Per File :
> ______________________________________________________________
>
> What should i do to resolve this problem.
>
> Best regards
>
> Benjamin
>
>
>>
> --
> Brett Porter
> br...@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
