Visit Azul.com Support

1.11.0

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

Optimizer Hub 1.11.0

Release Date: April 7, 2025 - Release Notes PDF

New Features

  • Includes bug fixes for Optimizer Hub 1.10.1.

  • The REST API in Optimizer Hub has been improved and extended:

    • Previous endpoints have moved to a new address with new data formatting and paging.

    • Attributes were added to the existing entities to provide more data.

    • More information is available per JVM instance.

    • REST endpoints are documented based on the OpenAPI standard.

  • A new readiness endpoint /api/opthub-health/healthy is available and replaces /q/health. You can use this endpoint to determine when it is safe to route traffic to a newly started Optimizer Hub cluster. This endpoint is provided by the gateway component, instead of the other ones, which are provided by the mgmt-gateway.

    Returned states:

    • 200: OK

    • 300 and higher: Not OK

  • With the new Scaling API, you can instrument Optimizer Hub to temporarily increase the minimum number of vCPUs between a start and end timestamp. Multiple calls can be made to this API and Optimizer Hub will take all given timestamps and potential overlaps into account to start and stop the extra resources.

    See Sizing and Scaling your Optimizer Hub Installation for more info.

  • The Management Gateway component in Optimizer Hub is now installed by default. It has become an essential part of any deployment as it provides the REST APIs.

  • Azul Zing Builds of OpenJDK, version 25.02 and newer, provide a new command line option -XX:CNCLocalFallbackOptLevelLimit=<3,2,1,0> to define the OptLevel for local fallback. See Cloud Native Compiler JVM Options.

  • Secrets can be externally defined to allow you to manage Kubernetes secrets independent of the Optimizer Hub configuration. See Using Externally Defined Secrets for more info.

Bug Fixes

  • Optimizer Hub now requires you to specify enough vCores to provision at least one Compile Broker if you have used the full installation. The minimum number of vCores is 39. When this is not the case, one or more of the following messages can be found in the log files:

     
    The compile-broker's minimum replicas must be greater than 0
The gateway's minimum replicas must be greater than 0
The cache's minimum replicas must be greater than 0

  • Improvement in ReadyNow Orchestrator to reduce the time before it can serve profiles during a restart of Optimizer Hub with a pre-populated storage.