Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-13432

Purging/updating of debian extractor cache is done per-node, should be done on the master only

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: 4.16.0
    • Fix Version/s: 5.1.2
    • Component/s: Debian, Indexer
    • Labels:
      None
    • Sprint:
      Leap 7

      Description

      Artifactory holds filesystem cache of extracted debian metadata (the control file specifically). On HA, even non-primary nodes have their own cache - this is bad because the primary node is the only node that calculates metadata right now.

      An example use case is a package that needs to be republished with changes to the control file - if the deployment goes through one of the slave nodes, the slave node will delete the cached entry for the given .deb locally, but it will be useless because the primary node may have its own cache for it, which will be reused on the next calculation cycle.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                yuvalr Yuval Reches
                Reporter:
                uriahl Uriah Levy
                Assigned QA:
                Inbar Tal
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: