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

Artifactory losing track of the cachefs data size on the disk after an upgrade and a restart. Once Artifactory loses track of the cachefs size then it resets the amount of space used to 0 bytes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: 3 - High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 7.11.1
    • Component/s: None
    • Labels:
      None
    • Severity:
      High
    • Release Notes:
      Yes

      Description

      Description: Artifactory losing track of the cachefs data size on the disk after an upgrade and a restart. Once Artifactory loses track of the cachefs size then it resets the amount of space used to 0 bytes. Due to this issue Artifactory will allow cachefs size to grow continuously as every restart resets the cachefs used space to 0 and we can see this in the UI ->Storage Summary page. However when we check the disk where the cachefs exists we can see that the used space is much much higher then the maxCacheSize parameter set in the binarystore.xml. At this point the value set by maxCacheSize parameter in the binarystore.xml is no longer followed by Artifactory. 

      Expected behavior: Artifactory should never exceed the maxCacheSize value set in the binarystore.xml and should not lose track of the existing cachefs data size on the disk.

      Steps To Reproduce

      1. Install version 6.16.2. From my tests the issue effects any installation type. I have tried both docker installation type and debian installation of Artifactory. Make sure to use S3 template with cachefs maxCacheSize set to a small value like 5 GB for the tests. Upload some data (about 3GB) to Artifactory which should fill the cache folder on the disk. At this point everything will be working as expected.
      2. Now upgrade Artifactory to version 7.7.3 and restart Artifactory. You will notice that the Storage summary page in Artifactory will report 4KB as the used space in cachefs while the disk will have 3GB of cachefs. At this point Artifactory will again allow you to store another 5GB of cachefs data on top of the 3GB that already existed.
      3. Restart Artifactory after uploading/downloading some more additional data and you will notice that Artifactory has again reset the size and in the storage summary page you will notice the used space is 4KB again. This will continue and every restart will lead to the cachefs to keep growing until you are out of disk space.

      Possible Workaround: For now the only workaround is to delete the entire cachefs data from the disk if Artifactory needs to be restarted, so that the restart doesn't result in the cachefs growing beyond the set limit. This is not a good workaround as the entire cache needs to be re-downloaded from S3 bucket after a restart and this will result in additional costs for data transfer from the S3 bucket depending on how large is your cachefs.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              nadavy Nadav Yogev
              Reporter:
              nihalc@jfrog.com Nihal Reddy Chinna Choudhary
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Sync Status

                  Connection: RTFACT Sync
                  RTMID-23764 -
                  SYNCHRONIZED
                  • Last Sync Date: