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

Removing a docker component using its sha256 hash can cause performance degradation

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.14.0, 3.16.2
    • Fix Version/s: 3.17.0
    • Component/s: Database, Docker
    • Labels:

      Description

      There are several cases where removing a docker component (e.g. docker rmi) could block threads and subsequently impact the performance of the nexus server.

      The cases are:
      1. Trying to remove a docker component using a sha256 hash that no longer exists.
      2. Removing a docker component that was created using a pre-release version of nexus using it's sha256 hash.

      Symptoms are blocked threads and memory spike if nexus receives a number of docker digest based deletes.

      Thread dump shows multiple threads with names similar to this one:

      <command>sql.select from asset where bucket = :bucket and attributes[docker][content_digest] = :propValue</command> id=111 state=RUNNABLE
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jhill Joshua Hill
              Reporter:
              jhill Joshua Hill
              Last Updated By:
              Peter Lynch Peter Lynch
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  tigCommentSecurity.panel-title