Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 3.30.0, 3.37.3, 3.38.1
-
Fix Version/s: 3.39.0
-
Labels:
-
Story Points:5
-
Sprint:NXRM MadMax Sprint 32, NXRM MadMax Sprint 33
-
Notability:3
Description
ISSUE:
It looks like moving one GAV with the staging API triggers checking all maven metadata in the same group.
Each check is fast (20 ~ 30 ms) but when there are a few thousands GAVs in the group, the staging API can take a few minutes or more to complete.
REPRODUCE STEPS
- Create two hosted repositories: maven-hosted and maven-releases
- Generate dummy data (please check 55985_prepare.sh
)
- Enable DEBUG logging for "org.sonatype.nexus.repository.maven.internal"
- Move only one version 1.8:
curl -D- -u admin:admin123 -X POST 'http://localhost:8081/service/rest/v1/staging/move/maven-releases?repository=maven-hosted&maven.groupId=test.example55985&maven.artifactId=my-app1&maven.baseVersion=1.8'
EXPECTED BEHAVIOUR:
In the nexus.log, not many DEBUG logging line: org.sonatype.nexus.repository.maven.internal.hosted.metadata.MetadataBuilder - -> GAbV: ...
Or, if this check is necessary, it should be checked parallely.
ACTUAL BEHAVIOUR:
It checked 26 GAVs:
$ grep -E 'qtp887917427-129.+MetadataBuilder - -> GAbV' ./sonatype-work/nexus3/log/nexus.log -c
26
Attachments
Issue Links
- is related to
-
NEXUS-30448 Rebuilding maven-metadata.xml on slower PostgreSQL could take extremely long time
-
- Closed
-
-
NEXUS-31396 Requesting GA maven-metadata.xml checks all GAVs under the repository
-
- Closed
-
- mentioned in
-
Page Loading...