Skip to main content
Version: 2.14

Ververica Platform 2.3.3

Release Date: 2021-02-04

Changelog​

Ververica Platform 2.3.3 continues to support Apache Flink® 1.10 and 1.11 under SLA.

This release adds support for Flink versions 1.10.3 and 1.11.3 and changes the configured memory allocator.

Memory Allocator​

The memory allocator of our provided Flink images has been changed to jemalloc. This change has been shown to reduce memory fragmentation, preventing OOMKilled containers when using the RocksDb state backend. The open source Apache Flink® community has made a similar change to their images.

Please check out the Flink 1.10.3 release announcement for details about this Flink release.

Please check Ververica Platform Docker Images for all available Apache Flink® images and additional tags.

Please check out the Flink 1.11.3 release announcement for details about this Flink release.

In addition to the fixes mentioned above, this release already contains a backport of FLINK-21132, which is not included in the latest upstream release of Apache Flink®.

Please check Ververica Platform Docker Images for all available Apache Flink® images and additional tags.

Improvements​

Deployment​

  • Prior to this release, substitution of environment variables for entries in the Flink configuration required a writable container file system. The substitution logic has been moved into the Flink runtime, allowing substitution with read-only file systems. For this change to take effect, you have to use Flink version 1.10.3 / 1.11.3 or later.

Resource Usage Tracking​

  • It is now possible to track used CPU resources per namespace and let users with the admin role generate usage reports. Please check out the Resource Usage Tracking page for details about how to enable and use this feature.

Bug Fixes​

Universal Blob Storage​

  • Prior to this release, configuration of Universal Blob Storage for S3 only allowed the s3 scheme. Starting with this release, you can use any of the S3 FileSystem schemes supported by Flink, i.e. s3, s3a, or s3p.

Upgrade​

We recommend upgrading via Helm using the following commands:

    helm repo add ververica https://charts.ververica.com
    helm upgrade [RELEASE] ververica/ververica-platform --version 4.3.3 --values custom-values.yaml