-
Bug
-
Resolution: Fixed
-
Medium
-
7.14.0, 8.0.0, 8.9.0, 8.19.0, 9.0.0, 9.3.0
-
1
-
Severity 3 - Minor
-
1
-
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
- Setup mirrors.
- Enable debug logging on the mirrors.
- Push some content in a mirrored repository
- 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.
- 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.