Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-29502

'CacheInfo missing for' / 'assuming stale content' WARNs written to the log when on PostgreSQL

    Details

    • Story Points:
      2
    • Sprint:
      NXRM Sentinels Sprint 29, NXRM Sentinels Sprint 30, NXRM Sentinels Sprint 31
    • Notability:
      3
    • InvestmentLayer:
      customer-driven
    • Aha Concept:
      non-concept

      Description

      Problem
      WARN messages such as the following are written to the logging when fetching NPM packages:

       2021-11-09 12:01:48,649+0000 WARN  [qtp2132649631-111] admin com.sonatype.nexus.repository.group.deploy.internal.GroupWriteFacetImpl - CacheInfo missing for NpmContent{payload=NpmStreamPayload{stream=com.sonatype.nexus.repository.content.npm.internal.NpmFacetSupport$$Lambda$1681/1790802592@1306e635, size=-1, contentType='application/json'}, attributes='{etag=ace6c11952af25c8f72277ac0d42d3a81cd4c033, org.sonatype.nexus.repository.content.Asset=AssetData{assetId=2, path='/npm', kind='PACKAGE_ROOT', componentId=null, component=null, assetBlobId=2, assetBlob=AssetBlobData{assetBlobId=2, blobRef=default@F310BF1A-B70767FA-91B6D2F0-F407A95C-E03067CA:e4173410-5cab-41b6-95ce-d5264ecd3182, blobSize=16654724, contentType='application/json', checksums={md5=bf21ae74dba59b4be66ef86bd26d8592, sha1=ace6c11952af25c8f72277ac0d42d3a81cd4c033}, blobCreated=2021-11-09T11:59:48.895Z, createdBy='admin', createdByIp='127.0.0.1'}, lastDownloaded=2021-11-09T11:59:48.915584Z} AbstractRepositoryContent{repositoryId=2, attributes=NestedAttributesMap{parent=null, key='attributes', backing=null}, created=2021-11-09T11:59:48.896511Z, lastUpdated=2021-11-09T11:59:48.915584Z}, last_modified=2021-11-09T11:59:48.895Z}'}, assuming stale content.

      There are no issues fetching the packages (no 404s or 502s), it's just these warnings are appearing and filling up the logging.

      Steps to reproduce

      • install NxRM3 with PostgreSQL
      • create an NPM proxy repository targeting https://registry.npmjs.org
      • create an NPM group repository and add the above to the group
      • configure NPM client to target the NPM group you've just configured
      • run npm install....

      Observed Behaviour
      The WARNs appear in the logging for every fetch.

      Notes

      • The issue is not reproducible when using OrientDB.
      • The logs fill pretty rapidly, see attached WARN_logging_single_package.log
      • I didn't test H2 so it may not be specific to PostgreSQL (but certainly not reproducible on OrientDB)

      Expected

      Do not spam log files with otherwise harmless log messages, particularly at INFO or above levels.
      Figure out why this logging happens and neuter it if harmless.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mpiggott Matthew Piggott
              Reporter:
              astrachan Alex Strachan [X] (Inactive)
              CC:
              Tom Dierckx
              Last Updated By:
              Michael Prescott Michael Prescott
              Team:
              NXRM - Sentinels
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title