Release esb3024-1.18.0

Build date

2025-02-13

Release status

Type: production

Compatibility

This release is compatible with the following product versions:

• Orbit, ESB2001-3.6.2 (see Known limitations below)
• SW-Streamer, ESB3004-1.36.2
• Convoy, ESB3006-3.4.0
• Request Router, ESB3008-3.2.1

Breaking changes from previous release

• Configurations with an invalid entrypoint will be rejected.

Change log

• NEW: Support configuration feedback. concli provides very basic feedback [ESB3024-1165]
• NEW: Send HTTP requests from Lua code [ESB3024-1172]
• NEW: Add acd-metrics-aggregator service [ESB3024-1221]
• NEW: Add acd-telegraf-metrics-database service [ESB3024-1224]
• NEW: Make all Lua functions snake_case. timeToEpoch and epochToTime have been deprecated. [ESB3024-1246]
• FIXED: Content popularity parameters can’t be configured [ESB3024-1187]
• FIXED: acd-edns-proxy returns CNAME records in brackets. Hostnames were erroneously interpreted as IPv6 addresses. [ESB3024-1276]

Deprecations from previous release

• Lua function epochToTime has been deprecated in favor of epoch_to_time.
• Lua function timeToEpoch has been deprecated in favor of time_to_epoch.
• The session proxy has been deprecated. Its functionality is replaced by the new “Send HTTP requests from Lua code” function.

System requirements

• The ACD Router requires a minimum CPU architecture level of x86-64-v2 due to inclusion of Oracle Linux 9 inside the container. While all modern CPUs support this archetecture level, virtual hypervisors may default to a CPU type that has more compatibility with older processors. If this minimum CPU architecture level is not attained the containers may refuse to start. See Operating System Compatibility and Building Red Hat Enterprise Linux 9 for the x86-64-v2 Microarchitecture Level for more information.

Known limitations

• GUI version 3.0.2 or earlier will not work with this release.

• When configured to use TLS, acd-telegraf-metrics-database might log the following error message: http: TLS handshake error from <client ip>: client sent an HTTP request to an HTTPS server when receiving metrics from caches even though the Telegraf agents are configured to use TLS. The Telegraf logs on the caches do not show any errors related to this. However, the data is still received over TLS and stored correctly by acd-telegraf-metrics-database. The issue seemingly resolved itself during investigation and is not reproducible. Current hypothesis is a logging bug in Telegraf.

• The Telegraf metrics agent might not be able to read all relevant network interface data on ESB2001 releases older than 3.6.2. The predictive load balancing function host_has_bw() and the health check function interfaces_online() might therefore not work as expected.

  • The recommended workaround for host_has_bw() is to use host_has_bw_custom(), documented in Built-in Lua functions. host_has_bw_custom() accepts a numeric argument for the host’s network interface capacity which can be used if the data supplied by the Telegraf metrics agents do not contain this information.
  • It is not recommended to use interfaces_online() for ESB2001 instances until they are updated to 3.6.2 or later.