In the case of voluntary actions that cause an imbalance in the system redundancy, such as when doing a filestore migration, you may manually invoke rebalancing of redundancy using the Optimize System Storage REST API endpoint. Applying this endpoint raises a flag for Artifactory to run rebalancing following the next Garbage Collection. Note that, to expedite rebalancing, you can invoke garbage collection manually from the Artifactory UI.
Optimizing System Storage
After deployment, duplications of files bigger than the redundancy are expected and the garbage collector removes them after the optimization run. On each deploy operation to a shard, Artifactory checks if the checksum exists more than once. If the checksum exists more than once and the count of such repetitions is bigger than the number of redundancy, Artifactory triggers the optimization flag. When the next full garbage collection runs, the duplicates are removed. By default, the full garbage collection runs after 20 iterations and each iteration runs after four hours resulting in six iterations per day. For more information on garbage collection, see Garbage Collection.
Artifactory REST API provides an endpoint that allows you to raise a flag to indicate that Artifactory should invoke balancing between redundant storage units of a sharded filestore after the next garbage collection. Therefore, you can set the flag to the optimization flag manually. For information on the API, see Optimize System Storage.