A recent move to v2 cgroups by a number of Linux distributions (including Amazon Linux 2022 and Red Hat Enterprise Linux 9) highlights an issue in Ama

kPow for Apache Kafka: Amazon Corretto JVM Memory Issues

submited by

Style Pass

2022-05-16 10:00:15

A recent move to v2 cgroups by a number of Linux distributions (including Amazon Linux 2022 and Red Hat Enterprise Linux 9) highlights an issue in Amazon Corretto 11 where the JVM process can cause a Docker container to exit with OOMKilled errors. This issue applies to any Corretto 11 JVM process and is not specific to Kpow.

Corretto is the base image of our main Docker container. We expect the impact of this issue to be limited, and for it to be resolved in Corretto shortly.

This post provides an explanation of the issue and a temporary workaround to constrain the heap usage of Kpow when using our docker image.

Our users deploy Kpow in numerous ways – on-premises, in private or public cloud, via our JAR file, using our docker image, with our Helm charts in Kubernetes, or sometimes a mixture of each option in one organisation.

The base deliverable for each Kpow release is a Java JAR. When using the JAR directly we start the JVM with memory constraints, e.g.