-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command Router: Memory leak concerning Kafka Metrics (with many added/deleted topics) #3016
Comments
Micrometer 1.7.6 contains a fix - see micrometer-metrics/micrometer#2843. |
Besides the issue in Micrometer mentioned above, there is also an issue in the Kafka client itself.
|
calohmn
added a commit
to bosch-io/hono
that referenced
this issue
Jan 13, 2022
Micrometer 1.7.6 contains a fix regarding a Kafka metrics memory leak. Signed-off-by: Carsten Lohmann <[email protected]>
calohmn
added a commit
to bosch-io/hono
that referenced
this issue
Jan 13, 2022
Signed-off-by: Carsten Lohmann <[email protected]>
calohmn
added a commit
that referenced
this issue
Jan 13, 2022
Micrometer 1.7.6 contains a fix regarding a Kafka metrics memory leak. Signed-off-by: Carsten Lohmann <[email protected]>
calohmn
added a commit
that referenced
this issue
Jan 13, 2022
Signed-off-by: Carsten Lohmann <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On a Hono deployment using Kafka messaging, where many (test) tenants get created and removed again, the memory usage of the Command Router component steadily increases, so that after a certain time period (one week in our case) the pod gets OOM-killed.
Comparing heap dumps has revealed that the added
org.apache.kafka.common.metrics.KafkaMetric
objects related to the tenant topics cause the memory increase. They are currently not getting removed after the topics get deleted.The text was updated successfully, but these errors were encountered: