Currently, metadata for RPM, Debian, and select other packages are stored locally on each node in its $ARTIFACTORY_HOME/data/.cache and $ARTIFACTORY_HOME/data/.rpmcache locations.
These locations are not shared across nodes, and will be used even if a different location for the filestore is provided.
This can cause multiple problems when Artifactory reaches a large scale:
- The Artifactory installation directory requires more space to store the metadata
- On boarding new nodes requires downloading and calculating the metadata stored in these locations (If using an S3 bucket)
- HA nodes cannot share metadata from their cache to other nodes, causing delays
This behavior also happens on the Cloud Storage "eventual" folder, which cannot currently be configured to be on a different location.
A potential solution would be to apply the same implementation that allows for no-NFS on the Artifactory binary filestore. This has the added benefit of not requiring extra customization.
Another solution would be to allow users to specify a non-default directory for these caches, to allow a larger disk to be used for data storage.