General release notes for the ZDM Proxy.
Build artifacts are available at Docker Hub.
For additional details on the changes included in a specific release, see the associated CHANGELOG-x.x.md file.
Fix too small buffer for LZ4 decompression.
Support LZ4 and snappy compression.
Support protocol v5.
New configuration setting ZDM_BLOCKED_PROTOCOL_VERSIONS to block specific protocol versions at the proxy level.
Send request id in the request payload (currently supported by Astra only).
Fix CQL stream ID validation for internal heartbeat mechanism.
Do not print misleading warning message when processing SUPPORTED response to internal heartbeat.
Upgrade software dependencies to benefit from performance improvements:
- ANTLR to 4.13.1
Fix race condition that caused a crash while reconnecting the control connection
Ignore forwarding CQL requests for DSE Insights Client to target cluster
Upgrade software dependencies to resolve vulnerabilities:
- GoLang to 1.24.2
Upgrade software dependencies to resolve vulnerabilities:
- GoLang to 1.22
- github.com/prometheus/client_golang to 1.11.1
- google.golang.org/protobuf to 1.33.0
Support providing configuration of ZDM with YAML file.
Support SAI queries and third-party authenticators.
Enables read only workloads to work correctly with ZDM-Proxy and Datastax Astra.
Astra terminates idle connections after a period of inactivity and Datastax Drivers send periodic heartbeats by default if the user does not send any request in a time interval so this is not an issue in a normal deployment.
With ZDM-Proxy in the mix, there won't be an issue if the workload has both reads and writes because if a heartbeat is sent by the client application then the proxy will forward it to both Origin and Target. However, if the client application can have time periods where only read requests are sent then the client application will not send a heartbeat (because requests are being sent through the connection) but the SECONDARY cluster will not receive any requests during that time period (reads are sent to PRIMARY only) which can cause a disconnect due to an idle connection.
This release enables the ZDM-Proxy to independently send heartbeats on the SECONDARY cluster connection if that connection has not seen any activity over a certain period of time which should fix the issue of disconnects happening when a client application was only sending read requests to the proxy.
Open-source release that also includes renaming of the product, public documentation launch and a revamp of configuration and metrics.