Artifactory keeps an in memory map of the binaries inside the cache-fs path. This map is initialized during startup. A client may need to symlink this location. In this case, the cache-fs will consider the cache symlink a file and won't traverse the tree underneath it so essentially the map will only contain a single entry which is the "cache" dir symlink itself.
This causes the cache path to grow uncontrollably, because every time the server is restarted we lose the history of all the entries that were added during the last uptime cycle. This is because our LRU cleanup mechanism relies on the existence of all the binaries under the cache dir in this map in order to remove them when the space limit is exceeded.