Following the setup instructions will result in a BullFrog install that does not manage the retention and thus the size of the databases in /data/.
As an example, 5 weeks after installing BullFrog, we had a 20+GB /data/data.h2.db file. This can easily fill up disk partitions that are not over-provisioned and at the observed growth rate, would fill up any sized partition in a relatively short amount of time.
Further, this path is not one of the ones the Artifactory app will monitor and warn for disk space, as it does for binary storage directories, so users would be blind to the issue until it was causing critical issues (such as blocking new binary uploads to Artifactory).
Some sort of retention or at least age based compression of older data should be a required part of the default install/config to prevent stability issues with Artifactory instances that employ BullFrog.
When BullFrog is installed, some sort of disk space monitoring on the install partition should produce a warning in the Artifactory UI or via other notification prior to the disk filling up and causing an Artifactory outage.
Following the setup instructions will result in a BullFrog install that does not manage the retention and thus the size of the databases in/data/.
As an example, 5 weeks after installing BullFrog, we had a 20+GB/data/data.h2.db file. This can easily fill up disk partitions that are not over-provisioned and at the observed growth rate, would fill up any sized partition in a relatively short amount of time.
Further, this path is not one of the ones the Artifactory app will monitor and warn for disk space, as it does for binary storage directories, so users would be blind to the issue until it was causing critical issues (such as blocking new binary uploads to Artifactory).