Visit Support

Configuring the ReadyNow Orchestrator

Table of Contents
Need help?
Schedule a consultation with an Azul performance expert.
Contact Us

When you use the Optimizer Hub ReadyNow Orchestrator, JVMs all write profile log candidates to unique profile names on the service. ReadyNow Orchestrator gathers all of the candidates for a profile name and decides which is th best candidate to serve to JVM clients requesting that profile name.

When considering what settings are set on the client versus on the service:

  • Individual JVMs decide when ReadyNow Orchestrator should consider their profile log is a suitable candidate for sharing with other JVMs. They can also override server-side defaults for profile log nomination candidates and maximum profile log size.

  • ReadyNow Orchestrator also controls the rules for where to store ReadyNow profile logs, when to clean up old logs, and service-wide defaults for profile log candidate nomination and maximum profile log size.

Duration Configuration

You specify the value of duration properties in the format PnDTnHnMn.nS, where n is the relevant days, hours, minutes or seconds part of the duration.

Configuring Clean Up of Old Profile Logs

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.

You can also configure the 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

ReadyNow Orchestrator triggers cleanup when you have used around 60% of the available space in your storage. If you are using a persistent volume to back up your storage, ReadyNow Orchestrator calculates the threshold for triggering clean up automatically. If you are using S3 or Azure Blob Storage, there is no reliable way for ReadyNow Orchestrator to calculate the size of the blob storage. You must therefore specify the size using the readyNowOrchestrator.cleaner.externalPersistentStorageSoftLimit property, which by default, is 10Gb.

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 the ReadyNow Orchestrator receive an error.

ReadyNow Orchestrator Defaults

Optimizer Hub admins can set the following global defaults for ReadyNow profiles in values-override.yaml:

Option Description Default


Limit of rolling profile history entries



Enabling of caching the chunk content on the gateway



The fixed size of chunk content cache on the gateway



Time required after the last profile update, after which the profile is considered completed and updates are no longer possible, duration specified in format PnDTnHnMn.nS.



The number of concurrent copies of a specific generation ReadyNow Orchestrator will accept before it tells other JVMs trying to write the same generation of the same profile name to stop



Maximum number of generations ReadyNow Orchestrator will accept for a profile name. Note that here is no 'unlimited' value available



Limit on the input profile size, in bytes. No limit by default



Enabling of automatic repository clean-up



When your storage is backed by azure-blob or s3 storage, this determines the threshold for the blob data usage, at which the ReadyNow Orchestrator initiates its cleanup process.

When your storage is backed by a persistent storage volume, this threshold is calculated automatically.



Time limit after which the profile name will be removed if it was not requested within the given duration specified in format PnDTnHnMn.nS.

By default, no limit is defined.