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

Proxy/Group repository fails to serve cached content during refreshing from remote

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Do
    • Affects Version/s: 3.29.2, 3.30.0
    • Fix Version/s: None
    • Component/s: Proxy Repository
    • Labels:
    • Notability:
      2

      Description

      How to reproduce

      1. Create a proxy
        Any format will work, I'll assume Docker, for the rest of report.
      2. Pull some data from remote via created proxy
        For example pull an image docker pull 192.168.1.84:8082/centos
      3. Invalidate the proxy cache
        Invalidating cache will force next request to check whether remote content has changed
      4. Run 101+ parallel requests for the same asset that has been previously cached (and expired, but still present)
         You can use attached Python script or WRK, e.g. wrk -t12 -c200 -d1m http://localhost:8081/repository/docker-proxy/v2/-/blobs/sha256:7a0437f04f83f084b7ed68ad9c4a4947e12fc4e1b006b38129bac89114ec3621

      Actual
      Proxy repository will return 503 Service Unavailable, but if you did reproduction step via a group repository containing a proxy repository the actual responses would be 404 Not Found even though the content is already present in NXRM.

      Expected
      Expected the content to be served since it's already present in NXRM, even if the cache is invalidated, the content is there.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mkalachov Maksym Kalachov
              Reporter:
              dsawa Dawid Sawa
              Last Updated By:
              Joe Tom Joe Tom
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title