Configuring Blob Storage Auto Cleanup

Table of Contents

Code Cache Cleanup
ReadyNow Profile Log Cleanup

Need help?

Schedule a consultation with an Azul performance expert.

Optimizer Hub uses your cloud provider’s blob storage as the main persistence mechanism. Artifacts persisted to blob storage are:

ReadyNow Orchestrator’s saved profile logs
Cloud Native Compiler’s code cache of previously performed compilations

Optimizer Hub includes an auto cleaner mechanism to clean up unused data. Cleanup for ReadyNow profile logs and code cache entries are configured separately.

Note	Due to the nature of cloud blob storage and how Optimizer Hub stores data, any blob storage limit settings are approximate limits and cannot be enforced exactly.

Code Cache Cleanup

You specify the target size for the blob storage that Optimizer Hub should not exceed, as well as how often Optimizer Hub should check if cleaning is necessary.

The following are the default values, which you can modify in your values-override.yaml file:

 codeCache:
  storageType: blobstore
  cleaner:
    enabled: true
    targetSize: "107374182400" # 100GiB, use quotes for large numbers
    interval: PT2H # 2 hours

You can check the used storage size in the Grafana dashboard in the "Details: cache” section.

ReadyNow Profile Log Cleanup

ReadyNow Orchestrator performs automatic cleanup of unused profile logs in order to fit collected data in the configured storage. When the data size in your storage exceeds a threshold, ReadyNow Orchestrator deletes old profile logs, thus guaranteeing that a promoted profile log is available for all profile names.

The following are the default values, which you can modify in your values-override.yaml file:

 readyNowOrchestrator:
  cleaner:
    enabled: true
    externalPersistentStorageSoftLimit: "10Gi"
    targetSize: 0 # use only to override auto-settings
    warningSize: 0 # use only to override auto-settings
    keepUnrequestedProfileNamesFor: 0
    keepDebugOnlyGenerationProfilesFor: "P7D"

By default, the ReadyNow profile log auto cleaner deletes all of the profiles in your ProfileName except for the promoted profile. This includes debug profiles that you recorded after the ProfileName had already reached its readyNowOrchestrator.producers.maxPromotableGeneration limit.

You can configure ReadyNow Orchestrator to delete unused profile names completely after a given duration using the readyNowOrchestrator.cleaner.keepUnrequestedProfileNamesFor property in your values-override.yaml. For example, to keep unused profiles for 5 days, use the following:

 readyNowOrchestrator.cleaner.keepUnrequestedProfileNamesFor=P5D

Note that depending on your usage, ReadyNow Orchestrator’s clean-up mechanism may not be able to keep the actual size of your stored profiles below the size of your storage. When you reach 90% usage, a warning is printed in the log of the gateway service. If your storage fills up completely, JVMs attempting to write to ReadyNow Orchestrator receive an error.