Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-19716

Repository size calculated unnecessarily on mirrors

XMLWordPrintable

      Issue Summary

      Repository size is calculated and stored in the mirror database even when there is no consumer of repository size on the mirrors.

      Steps to Reproduce

      1. Setup mirrors.
      2. Enable debug logging on the mirrors.
      3. Push some content in a mirrored repository
      4. Wait for the GC to be performed for this repository on mirrors. Try deleting shared/data/repositories/<REPO_ID>/app-info/packrefs.ts file before pushing changes to trigger GC after the changes are synced on mirrors.
      5. Check the contents of bb_repo_size table on the mirrors.

      Expected Results

      Repository size should never be calculated.

      Actual Results

      Repository size is calculated as noticed in the logs. Also the bb_repo_size table contains an entry for the repository size.

      Workaround

      From 8.9.20/8.19.10/9.2.1/9.3.0 onwards, set repository.size.notify.gc=false in the mirror's sidecar properties to disable size calculation. No workaround is available for the versions <=8.9 when the non-mesh SCM is used.

              Unassigned Unassigned
              mgoyal2@atlassian.com Manish
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: