Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.22.0
-
Fix Version/s: 3.25.0
-
Component/s: Logging, Scheduled Tasks
-
Notability:n/a
Description
A customer ran the Repair - Reconcile component db from blobstore task ( blobstore.rebuildComponentDB ) . The resulting task log was over 20MB in size. There were 69110 lines containing this type of WARN level message:
org.sonatype.nexus.blobstore.restore.maven.internal.MavenRestoreBlobStrategy - Skipping as no maven coordinates found and is not maven metadata
There is no information there about WHAT is being skipped. The log line is not helpful to debug problems.
Expected
The log line which has the message "Skipping as no maven coordinates found and is not maven metadata" should include WHAT is being skipped. Something reference-able that can be looked up ie. path or name or something relevant to what is being skipped.