Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-31982

Fix repeating "Unknown blob for key" WARN logs after cached blob is deleted

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2021.0
    • Fix Version/s: 2023.1, 2021.41
    • Component/s: Core, S3

      Description

      If a Document's cached blob(s) are deleted, processes that check for existent blobs (e.g. orphan blob garbage collection) will log "Unknown blob for key: " on every execution (see LocalBlobStore.java:318). Those that recur often can result in this log being repeated hundreds or thousands of times which can bloat the server log.

      Steps to Reproduce:

      1. In an environment configured to use S3, create a Document either using or attaching a file (e.g. Picture) and confirm the blob is uploaded and stored.
      2. Navigate to the instance's nuxeo.tmp.dir directory and locate the nxbincache folder where the cached binary is stored.
      3. Delete the cached binary.
      4. Run orphan blob GC process at least twice using the following command:
        curl -X DELETE -u Administrator:Administrator http://localhost:8080/nuxeo/api/v1/management/binaries/orphaned

      Expected behavior: "Unknown blob for key: " WARN log is outputted on the first execution and is no longer generated following.

      Actual behavior: "Unknown blob for key: " WARN log is outputted on each execution of the process.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: