Cold Storage includes several properties that can be used to configure and optimize its performance.
The list of parameters and their corresponding values that are shown below are for reference only. It is highly recommended that you do not change these values.
Live Artifactory Properties
The following properties can be configured in the Live Artifactory's
Number of threads that will be used per policy to archive items.
Number of threads that will be used to restore items.
Number of HTTP connections that are allowed to deploy artifacts from the Live instance to the Cold instance.
Maximum socket timeout for an HTTP connection.
Number of HTTP peers per route that are allowed to deploy artifacts from the Live instance to the Cold instance.
Setting for how often the Live instance will try to pull restored items from the Cold instance.
Setting for how many restored items will be pulled from the Cold instance to the Live instance.
Approximate maximum allowed bandwidth for all restore operations.
Error threshold to stop restore operation.
Setting for how many items are fetched from the database during archive policy execution.
Approximate max allowed bandwidth for a single archive policy execution.
Stop execution if there are 10% errors during an archive process.
Specifies the maximum amount of packages archived per one batch.
Specifies the maximum number of retries in the event of Cold Server communication failure.
Specifies the delay (in seconds) between retries if there is a Cold Server communication failure.
Cold Artifactory Properties
The following properties can be configured in the Cold Artifactory System YAML.
Number of threads that will be used when processing the restore request.
By default, on the Cold Artifactory instance, the cron job rate to check the restore status for each archived item is 120 seconds (2min). This can be reconfigured for cost optimization.
Interval for the cleanup job.
The following property can be configured in the Cold Artifactory's
The default maximum number of artifacts that can be restored during a single run is 30k. This value can be configured higher or lower using the